From: Ricardo Wurmus <rekado@elephly.net>
To: 30094@debbugs.gnu.org
Subject: bug#30094: [wishlist] better support for alternative languages
Date: Fri, 12 Jan 2018 23:45:36 +0100 [thread overview]
Message-ID: <876086wvan.fsf@elephly.net> (raw)
Hi Guilers,
since Guile supports alternative language implementations like Wisp it
would be nice if it could interpret files that contain code written in
other languages, without having to specially cater to them.
If GUILE_LOAD_PATH contains a file “foo.wisp” written in Wisp it would
be nice if Guile would automatically read it with the Wisp language.
The same applies to “load”, which only supports Scheme code.
Another idea might be to adopt the “#lang” macro from Racket to inform
Guile about the language that is used in the current file.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next reply other threads:[~2018-01-12 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 22:45 Ricardo Wurmus [this message]
2018-08-19 21:24 ` bug#30094: proposed code for alt languages Matt Wette
2018-09-04 13:43 ` bug#30094: patch for adding external lang support Matt Wette
2018-09-04 14:00 ` Matt Wette
2018-09-05 1:35 ` bug#30094: test script Matt Wette
2018-09-23 17:29 ` bug#30094: load-lang patch Matt Wette
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=876086wvan.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=30094@debbugs.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).