From: "Robert Thorpe" <rthorpe@realworldtech.com>
Subject: Re: State-machine based syntax highlighting
Date: 7 Dec 2006 06:39:33 -0800 [thread overview]
Message-ID: <1165502373.932709.15860@79g2000cws.googlegroups.com> (raw)
In-Reply-To: <1165501630.172348.157180@j72g2000cwa.googlegroups.com>
spamfilteraccount@gmail.com wrote:
> Robert Thorpe wrote:
> >
> > The Emacs "Semantic" package already does much of this, so do some
> > other editors.
>
> It would make more sense to create one such parser than reimplementing
> parsing in every editor...
In many ways it would. But I expect it will be reimplemented in every
editor, for several reasons:-
* The insides of different editors work very differently
* External dependencies make building harder and irritate people
* Elisp is considerably nicer than many programming languages
reimplementing is not so hard
* Many people will make parsers as closed-source, or refuse to assign
copyright to the FSF
* People don't like helping other editors so they don't offer
functionality in an easily usable form
* GNU will not want to offer _parsers_ in an easily usable form,
because doing so would allow proprietery compilers to be built very
easily.
I'm not saying this is necessarily the best way, but I expect it's what
will happen.
> I did a quick search and found this page
>
>
> http://harmonia.cs.berkeley.edu/harmonia/projects/harmonia-mode/doc/index.html
>
> with a demo xemacs package with syntax highlighting and stuff. Looked
> interesting.
Interesting.
next prev parent reply other threads:[~2006-12-07 14:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 6:14 State-machine based syntax highlighting spamfilteraccount
2006-12-07 10:53 ` Robert Thorpe
2006-12-07 11:56 ` spamfilteraccount
2006-12-07 12:42 ` Robert Thorpe
2006-12-07 14:27 ` spamfilteraccount
2006-12-07 14:39 ` Robert Thorpe [this message]
2006-12-07 17:02 ` spamfilteraccount
2006-12-07 17:42 ` Stefan Monnier
[not found] ` <mailman.1644.1165513359.2155.help-gnu-emacs@gnu.org>
2006-12-07 18:35 ` spamfilteraccount
2006-12-07 18:57 ` Robert Thorpe
2006-12-07 20:24 ` Perry Smith
2006-12-08 7:33 ` spamfilteraccount
2006-12-08 8:10 ` Tim X
2006-12-08 8:36 ` spamfilteraccount
2006-12-08 16:17 ` Robert Thorpe
2006-12-08 21:14 ` spamfilteraccount
2006-12-09 2:08 ` Stefan Monnier
2006-12-09 2:06 ` Stefan Monnier
2006-12-09 3:24 ` Lennart Borgman
2006-12-08 13:14 ` Leo
2006-12-08 14:00 ` Robert Thorpe
2006-12-09 2:10 ` Stefan Monnier
[not found] ` <mailman.1672.1165586758.2155.help-gnu-emacs@gnu.org>
2006-12-08 14:17 ` Robert Thorpe
2006-12-08 21:17 ` spamfilteraccount
[not found] ` <mailman.1653.1165523111.2155.help-gnu-emacs@gnu.org>
2006-12-08 10:01 ` Robert Thorpe
2006-12-07 19:02 ` Stefan Monnier
2006-12-07 19:29 ` spamfilteraccount
2006-12-08 14:43 ` Robert Thorpe
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=1165502373.932709.15860@79g2000cws.googlegroups.com \
--to=rthorpe@realworldtech.com \
/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).