From: "Pascal J. Bourguignon" <pjb@informatimago.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Defining functions on the fly
Date: Tue, 16 Jun 2015 18:13:11 +0200 [thread overview]
Message-ID: <87oakftyw8.fsf@kuiper.lan.informatimago.com> (raw)
In-Reply-To: mailman.5090.1434454815.904.help-gnu-emacs@gnu.org
Andreas, you might be interested in reading:
https://www.ics.uci.edu/~taylor/ics228/SynGen.pdf
and
Teitelbaum, T.; T. Reps (September 1981). "The Cornell Program
Synthesizer: A syntax-directed programming
environment". Communications of the ACM 24 (9):
563–573. doi:10.1145/358746.358755.
if you can get your hands on it.
Check also: https://en.wikipedia.org/wiki/Structure_editor
Basically, you could generate the whole mode all the structured editing
commands, from a grammar of the language you want to edit.
And since you could include in the grammar, grammars of other languages
when you have such escape, such as html scripts, or php, etc, you would
get automatically "multi-mode" structured editing modes.
Now, when you generate code (eg. a programming language compiler), it is
perfectly normal to have parts that are generated, and functions and
stubs that are written once for all for all the programs: a run-time
library.
Your code generate would naturally bind mode commands whose name would
be prefixed by the name of the grammar (= the mode), but the run-time
library would be the same for all those generated mode, and would have a
library prefix instead.
--
__Pascal Bourguignon__ http://www.informatimago.com/
“The factory of the future will have only two employees, a man and a
dog. The man will be there to feed the dog. The dog will be there to
keep the man from touching the equipment.” -- Carl Bass CEO Autodesk
next prev parent reply other threads:[~2015-06-16 16:13 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 9:24 Defining functions on the fly Andreas Röhler
2015-06-15 9:32 ` Dmitry Gutov
2015-06-15 9:47 ` Alexis
2015-06-15 10:20 ` Andreas Röhler
2015-06-15 10:37 ` Alexis
2015-06-15 10:41 ` Michael Heerdegen
2015-06-15 10:42 ` Tassilo Horn
2015-06-15 11:01 ` Alexis
2015-06-15 11:19 ` Michael Heerdegen
2015-06-15 11:24 ` Tassilo Horn
2015-06-15 11:31 ` Michael Heerdegen
2015-06-15 10:00 ` Tassilo Horn
2015-06-15 10:33 ` Andreas Röhler
[not found] ` <mailman.5022.1434361680.904.help-gnu-emacs@gnu.org>
2015-06-15 12:52 ` Stefan Monnier
2015-06-16 5:59 ` Andreas Röhler
2015-06-16 7:01 ` Tassilo Horn
2015-06-16 9:22 ` Andreas Röhler
2015-06-16 11:12 ` Tassilo Horn
2015-06-16 11:40 ` Andreas Röhler
2015-06-16 13:10 ` Tassilo Horn
2015-06-16 15:46 ` Andreas Röhler
[not found] ` <mailman.5109.1434469628.904.help-gnu-emacs@gnu.org>
2015-06-16 22:34 ` Stefan Monnier
[not found] ` <mailman.5090.1434454815.904.help-gnu-emacs@gnu.org>
2015-06-16 16:13 ` Pascal J. Bourguignon [this message]
2015-06-16 18:30 ` Andreas Röhler
2015-06-16 9:42 ` Andreas Röhler
[not found] ` <mailman.5084.1434446560.904.help-gnu-emacs@gnu.org>
2015-06-16 9:50 ` Pascal J. Bourguignon
2015-06-16 10:26 ` Andreas Röhler
[not found] ` <mailman.5087.1434450412.904.help-gnu-emacs@gnu.org>
2015-06-16 11:35 ` Pascal J. Bourguignon
[not found] ` <mailman.5085.1434447782.904.help-gnu-emacs@gnu.org>
2015-06-16 22:32 ` Stefan Monnier
[not found] ` <mailman.5075.1434434385.904.help-gnu-emacs@gnu.org>
2015-06-16 22:23 ` Stefan Monnier
2015-06-17 6:13 ` Andreas Röhler
[not found] ` <mailman.5137.1434522533.904.help-gnu-emacs@gnu.org>
2015-06-17 14:30 ` Stefan Monnier
2015-06-17 16:40 ` Andreas Röhler
[not found] <mailman.5020.1434360277.904.help-gnu-emacs@gnu.org>
2015-06-15 9:57 ` Pascal J. Bourguignon
2015-06-15 11:21 ` Andreas Röhler
2015-06-15 11:52 ` Tassilo Horn
2015-06-15 12:06 ` Andreas Röhler
2015-06-15 12:43 ` Andreas Röhler
2015-06-15 23:51 ` Gene
2015-06-16 1:14 ` Stefan Monnier
2015-06-17 0:24 ` Gene
2015-06-17 1:12 ` Stefan Monnier
2015-06-16 5:47 ` Andreas Röhler
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oakftyw8.fsf@kuiper.lan.informatimago.com \
--to=pjb@informatimago.com \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.