unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Damien Mattei <damien.mattei@gmail.com>
To: Christine Lemmer-Webber <cwebber@dustycloud.org>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Guile Steel: a proposal for a systems lisp
Date: Sun, 7 Aug 2022 23:12:07 +0200	[thread overview]
Message-ID: <CADEOaddSmSkNz4xWLPxo+dYg0kAb1VL7bpOw6=UJy=bFBWyfnA@mail.gmail.com> (raw)
In-Reply-To: <87czdbkdns.fsf@dustycloud.org>

On Sun, Aug 7, 2022 at 10:21 PM Christine Lemmer-Webber <
cwebber@dustycloud.org> wrote:

>
> Damien Mattei <damien.mattei@gmail.com> writes:
>
> > 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,
>
>
> > perhaps i'm wrong, but Chicken seems to have strict types as options:
> > http://wiki.call-cc.org/man/5/Types
>
> Interesting.  Any examples of it in action, personal use experience,
> etc?  I wonder how it handles the famous challenges of keeping that
> safety between both statically typed and dynamically typed parts, which
> turned out to be extremely expensive, far more than dynamic scoping,
> in Racket: https://www2.ccs.neu.edu/racket/pubs/popl16-tfgnvf.pdf
> (though there is work being done to make it better, hopefully...
> it may have progressed a lot since I last looked, probably has.)
>

i'm sorry but i almost never used Chicken...

>
> > about Bigloo the best answer would be to ask to author himself but i
> > used Bigloo a little to produce JVM class files only, not C obj files,
> > and it can be declared some statically typed variable i think in both
> > C and Java targets:
> > see:
> > https://www-sop.inria.fr/mimosa/fp/Bigloo/manual.html#G82
> > and mostly:
> > https://www-sop.inria.fr/mimosa/fp/Bigloo/manual-chapter25.html
> > Regards,
> > Damien
>
> Hm... "Warning: All type annotations are ignored by the interpreter."
>
> i suppose in the interpreter, code being not compiled, Bigloo act as a
> normal Scheme REPL and typing is ignored, but in compiled modules it works
> well.
>


      reply	other threads:[~2022-08-07 21:12 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
2022-08-07 20:17       ` Christine Lemmer-Webber
2022-08-07 21:12         ` Damien Mattei [this message]

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='CADEOaddSmSkNz4xWLPxo+dYg0kAb1VL7bpOw6=UJy=bFBWyfnA@mail.gmail.com' \
    --to=damien.mattei@gmail.com \
    --cc=cwebber@dustycloud.org \
    --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).