From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: Running non-scheme scripts: some thoughts
Date: Mon, 21 Jan 2013 17:19:20 +0100 [thread overview]
Message-ID: <87y5fmbjav.fsf@gnu.org> (raw)
In-Reply-To: <871ude93dx.fsf@pobox.com> (Andy Wingo's message of "Mon, 21 Jan 2013 12:33:46 +0100")
Hello!
Andy Wingo <wingo@pobox.com> skribis:
> On Sun 26 Aug 2012 23:16, ludo@gnu.org (Ludovic Courtès) writes:
[...]
>> guile -c '(display "good")' --language=ecmascript -c '2 + 2;'
>
> A first patch is attached. It depends on fluid->parameter and
> current-language being a parameter, patches I will push soonish.
>
> Getting this right is a bit tricky. First of all your example doesn't
> work because things stop after a "-c".
Right.
> In my attached patch, -c and -s respect the current language, but -l
> does not. I have the feeling that we should lower `current-language'
> to boot-9, to allow some flexibility while avoiding loading up the
> compiler unless we have to.
Yes, I think we should do whatever it takes to have -l honor the current
language.
> Another thing is that --lang does not appear to set the language for the
> first REPL invocation. We should fix that too, I suppose.
Agreed.
> Finally, -e uses the Scheme reader. -e is a pretty strange argument
> anyway, but hey.
That’s probably OK.
> Thoughts?
Bikeshedding: I’d prefer --language.
Perhaps we could have a couple of tests for -c, for instance, as shell
scripts in test-suite/standalone?
Thanks!
Ludo’.
next prev parent reply other threads:[~2013-01-21 16:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 15:31 Running non-scheme scripts: some thoughts Ian Price
2012-07-11 15:37 ` Andrew Gwozdziewycz
2012-07-11 22:15 ` Krister Svanlund
2012-07-12 3:12 ` nalaginrut
2012-07-12 3:27 ` William ML Leslie
2012-07-12 7:40 ` Neil Jerram
2012-08-26 21:16 ` Ludovic Courtès
2013-01-21 11:33 ` Andy Wingo
2013-01-21 16:19 ` Ludovic Courtès [this message]
2013-01-22 14:59 ` Andy Wingo
2013-01-22 21:45 ` 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=87y5fmbjav.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.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).