From: Juri Linkov <juri@linkov.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: "Mattias Engdegård" <mattiase@acm.org>,
"Lars Ingebrigtsen" <larsi@gnus.org>,
44554@debbugs.gnu.org, "Vladimir Nikishkin" <lockywolf@gmail.com>,
"Richard Stallman" <rms@gnu.org>
Subject: bug#44554: 27.1; Feature request: SRFI-62 style comments for Emacs Lisp.
Date: Thu, 12 Nov 2020 22:11:22 +0200 [thread overview]
Message-ID: <87zh3m72tx.fsf@mail.linkov.net> (raw)
In-Reply-To: <b0d26ad1-08fc-4261-a463-4cb2212b035b@default> (Drew Adams's message of "Thu, 12 Nov 2020 10:16:42 -0800 (PST)")
>> > No, not without modification. For example, #; would be treated as #
>> > and a comment removing the rest of the line by most existing lexers.
>> > And it's not just my code.
>>
>> Sure, it would be a new feature, and older lexers wouldn't understand
>> the new grammar, but that's true of (almost) any new language feature.
>
> If we had reader macros, and more generally a
> user-configurable reader, like Common Lisp, then
> maybe (?) users could adapt (e.g. disable or
> whatever) such new constructs programmatically,
> with Lisp.
I don't know if there is such a feature as transcompiling in Common Lisp
https://en.wikipedia.org/wiki/Source-to-source_compiler
but it should be possible to create a transpiler package that could help
to load Emacs Lisp files with newer syntax in older Emacs versions.
next prev parent reply other threads:[~2020-11-12 20:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 14:04 bug#44554: 27.1; Feature request: SRFI-62 style comments for Emacs Lisp Vladimir Nikishkin
2020-11-10 14:57 ` Lars Ingebrigtsen
2020-11-10 15:11 ` Vladimir Nikishkin
2020-11-10 17:17 ` Drew Adams
2020-11-13 18:32 ` João Távora
2020-11-10 19:31 ` Jean Louis
2020-11-11 5:40 ` Richard Stallman
2020-11-11 5:48 ` Jean Louis
2020-11-11 8:18 ` Vladimir Nikishkin
2020-11-11 8:25 ` Jean Louis
2020-11-11 14:18 ` Vladimir Nikishkin
2020-11-12 23:55 ` Eduardo Ochs
2020-11-11 8:29 ` Andreas Schwab
2020-11-11 22:50 ` Jose A. Ortega Ruiz
2020-11-10 17:17 ` Francesco Potortì
2020-11-10 23:18 ` Jose A. Ortega Ruiz
2020-11-11 16:10 ` Mattias Engdegård
2020-11-11 16:14 ` Vladimir Nikishkin
2020-11-11 16:25 ` Mattias Engdegård
2020-11-12 12:50 ` Lars Ingebrigtsen
2020-11-12 18:16 ` Drew Adams
2020-11-12 20:11 ` Juri Linkov [this message]
2020-11-12 20:44 ` Drew Adams
2020-11-13 0:38 ` Stefan Kangas
2020-11-13 13:24 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-13 13:47 ` Stefan Kangas
2020-11-13 14:07 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-13 21:03 ` Tassilo Horn
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zh3m72tx.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=44554@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.org \
--cc=lockywolf@gmail.com \
--cc=mattiase@acm.org \
--cc=rms@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).