From: Andy Wingo <wingo@pobox.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: BT Templeton <bpt@hcoop.net>, guile-devel@gnu.org
Subject: Re: *current-language*
Date: Sat, 07 Jan 2012 01:19:01 +0100 [thread overview]
Message-ID: <87aa60jrey.fsf@pobox.com> (raw)
In-Reply-To: <CA+U71=MwJUPK4w1AzUtK2zHdDCX8giBMCo=nP4pA63U3VpGknA@mail.gmail.com> (Noah Lavine's message of "Mon, 5 Dec 2011 19:36:35 -0500")
On Tue 06 Dec 2011 01:36, Noah Lavine <noah.b.lavine@gmail.com> writes:
>> I guess in general I'd prefer something like Racket's #!lang directives,
>> though I'm not opposed to this approach. Dunno!
>
> How about using language directives when available, and trying to
> guess the language when not?
I'm fine with this, FWIW.
> And about the directives, what should they be? ',language' is what we
> used to use at the REPL, and I was about to write an email arguing for
> that, until I realized that there is one big advantage to using the
> same thing as Racket - we might actually share some languages.
,language would be pretty cute, but I don't think it would work, as it
reads as (unquote language), and who knows what the binding of `unquote'
would be.
> Specifically, if someone had a Scheme file that started with '#!lang
> r5rs', it's possible that Guile and Racket could both run that file
> without modification. That seems pretty cool.
Yes, I agree, that would be nice. Perhaps we could even convince other
implementations that this is the right thing.
> Mixing other languages could be scary though.
Indeed :)
Regards,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2012-01-07 0:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-12 1:24 *current-language* BT Templeton
2011-07-09 1:03 ` *current-language* BT Templeton
2011-12-04 21:01 ` *current-language* Andy Wingo
2011-12-06 0:36 ` *current-language* Noah Lavine
2012-01-07 0:19 ` Andy Wingo [this message]
[not found] <201201070033.q070X8vT001386@winooski.ccs.neu.edu>
2012-01-07 1:56 ` *current-language* Eli Barzilay
2012-01-07 2:09 ` *current-language* Andy Wingo
2012-01-07 2:30 ` *current-language* Eli Barzilay
2012-01-07 22:41 ` *current-language* Ludovic Courtès
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=87aa60jrey.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=bpt@hcoop.net \
--cc=guile-devel@gnu.org \
--cc=noah.b.lavine@gmail.com \
/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).