From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: REPL reader of multi-language
Date: Fri, 30 May 2014 21:08:58 +0200 [thread overview]
Message-ID: <8761kn3wz9.fsf@gnu.org> (raw)
In-Reply-To: 1401438340.26418.33.camel@Renee-desktop.suse
Nala Ginrut <nalaginrut@gmail.com> skribis:
> So here's my problem, there's only one reader slot defined in each
> language type ,say, in (system base language). I have to implement just
> one reader to fit them all:
> 1. If I provide the interactive reader in Guile, the reader becomes
> inefficient. Because each time users input `Enter', the source code
> typed so far will be detected in lalr-parser, and exception would be
> caught when the line doesn't complete a chunk, then the REPL returns
> continue prompt, say '...'.
>
> 2. If I provide compiler reader, people have to type semicolon or ctrl+d
> to see the result.
Commit 65fa60 adjusted the REPL for multi-language support. In
particular that works fine with both Scheme/elisp and ECMAScript.
What exactly is missing for Lua to be usable at the REPL?
Ludo’.
next prev parent reply other threads:[~2014-05-30 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 8:25 REPL reader of multi-language Nala Ginrut
2014-05-30 12:48 ` Mike Gerwitz
2014-06-03 6:58 ` Nala Ginrut
2014-05-30 19:08 ` Ludovic Courtès [this message]
2014-06-03 6:36 ` Nala Ginrut
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=8761kn3wz9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).