unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Andrew Gwozdziewycz <apgwoz@gmail.com>
To: Damien Mattei <damien.mattei@gmail.com>
Cc: Christine Lemmer-Webber <cwebber@dustycloud.org>,
	Guile User <guile-user@gnu.org>
Subject: Re: Guile Steel: a proposal for a systems lisp
Date: Sun, 7 Aug 2022 09:02:13 -0700	[thread overview]
Message-ID: <0FF9B3B5-0CE8-4AAD-9E23-873757684D0B@gmail.com> (raw)
In-Reply-To: <CADEOadctuQ2L17diuCQh7BMnj7r6WfrdJxK7AQBeaiZe5ukPLw@mail.gmail.com>



> On Aug 7, 2022, at 07:47, Damien Mattei <damien.mattei@gmail.com> wrote:
> 
> On Sun, Aug 7, 2022 at 2:44 PM Christine Lemmer-Webber <
> cwebber@dustycloud.org> wrote:
> 
>> Bigloo is cool.  I think it falls under the same category of Chicken,
>> which I address towards the end of:
>> 
>>  https://dustycloud.org/blog/guile-steel-smelting-pot/
>> 
>> "Chicken Scheme compiles to C but doesn't strike me as qualifying for
>> this post's vague definition because it still has the usual
>> memory/dynamic typing overheads of Scheme. But go ahead and read
>> literally everything on more-magic.net anyway because that stuff is
>> great."
>> 
>> Same feels like it could be said of Bigloo, but if I'm wrong, lmk :)
>> 
> 
> perhaps i'm wrong, but Chicken seems to have strict types as options:
> http://wiki.call-cc.org/man/5/Types
>> 

The actual thing you want in a pre-scheme is as close to “normal”-C as possible. Pre-scheme’s primitives leave memory management up to you, compile to portable C types, and that’s by design. There’s no call/cc, no garbage collection, minimal support for tail calls; it’s restricted.

So, even if Chicken has strict types for compiled C, it’s still “Cheney on the MTA” garbage collected, and continuation supporting, not the general, as close to the system ABI as possible thing to build on and link against.





  reply	other threads:[~2022-08-07 16:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09 15:35 Guile Steel: a proposal for a systems lisp Christine Lemmer-Webber
2022-07-10  9:46 ` Blake Shaw
2022-07-10 12:14 ` Zelphir Kaltstahl
2022-07-11 11:13 ` Tim Van den Langenbergh
2022-07-15 12:08   ` Christine Lemmer-Webber
2022-08-06 22:38     ` Christine Lemmer-Webber
2022-07-11 13:10 ` Martin Becze
2022-08-07  9:28 ` Damien Mattei
2022-08-07 12:43   ` Christine Lemmer-Webber
2022-08-07 14:47     ` Damien Mattei
2022-08-07 16:02       ` Andrew Gwozdziewycz [this message]
2022-08-07 20:17       ` Christine Lemmer-Webber
2022-08-07 21:12         ` Damien Mattei

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0FF9B3B5-0CE8-4AAD-9E23-873757684D0B@gmail.com \
    --to=apgwoz@gmail.com \
    --cc=cwebber@dustycloud.org \
    --cc=damien.mattei@gmail.com \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).