From: Jan Rehders <cmdkeen@gmx.de>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Emacs mode for revised syntax
Date: Tue, 18 Dec 2007 22:58:02 +0100 [thread overview]
Message-ID: <C7E85349-C3EB-4D0E-AEA6-2A2AF51A7DC2@gmx.de> (raw)
In-Reply-To: <9f09a07a0712180653l4d2d218ay8cbd0bc9e6698b77@mail.gmail.com>
On 18.12.2007, at 15:53, Matthieu Dubuget wrote:
> I do not know if it is at will, but you only replied to myself,
> not to caml-list.
Oh, thank you for the notification. Here's my reply, again:
> - it would have to know wich syntax extension is used in each
> file. Until know, this knowledge is at building tools level? Would
> it be a good idea to move this information inside the files.
This also has the potential to simplify build files. This would be a
Good Thing(tm). On the other hand it could cause troubles if one would
want to use different extensions for different build configurations
(the conditional compilation extension might make this desirable).
This could probably be resolved by making the specified extension the
default one and allowing one to override it on the command line.
> Well would it be possible (and enough) or something to much difficult
> to add some more simple tools that would help any IDE?
> Like -dtypes does, for example.
> I mean simple tools that would make editors mode more simple to
> write (especially emacs, since this is the one I tend to use ;-)
A tool which emits something like an annotated AST containing
information like unique ids for names, their AST types etc. would be
very useful. It could be used for syntax highlighting as well as more
intricate tasks like refactoring tools. This might prove to be very
useful for IDE builders. I also made good experiences letting emacs
query an interactive toplevel for completions etc (for a custom
language). Steal.. erm getting inspiration from the lisp community
next prev parent reply other threads:[~2007-12-18 21:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 16:48 SerP
2007-12-17 17:26 ` [Caml-list] " Matthieu Dubuget
[not found] ` <E815649E-6215-4DAB-842F-C11DCC08518C@gmx.de>
[not found] ` <9f09a07a0712180653l4d2d218ay8cbd0bc9e6698b77@mail.gmail.com>
2007-12-18 21:58 ` Jan Rehders [this message]
2007-12-17 18:37 ` David Teller
2007-12-18 16:22 ` Berke Durak
2007-12-18 16:59 ` Nicolas Pouillard
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=C7E85349-C3EB-4D0E-AEA6-2A2AF51A7DC2@gmx.de \
--to=cmdkeen@gmx.de \
--cc=caml-list@yquem.inria.fr \
/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