From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: tromey@redhat.com
Cc: help-gnu-emacs@gnu.org, emacs-devel@gnu.org
Subject: Re: code completion
Date: Thu, 13 Mar 2008 00:17:34 +0100 [thread overview]
Message-ID: <47D8648E.4010100@gmail.com> (raw)
In-Reply-To: <m3iqzr62xm.fsf@fleche.redhat.com>
Tom Tromey wrote:
>>>>>> "Lennart" == Lennart Borgman (gmail) <lennart.borgman@gmail.com> writes:
>
>>>>> http://www.gccxml.org/
> Pascal> Will parsing of xml be faster in elisp than parsing C?
>>> You could always make it emit sexps :-)
>
> Lennart> Yes, seriously. Maybe those writing gcc-xml could accept it
> Lennart> as an option. I guess it should be a very simple change to
> Lennart> spit out elisp/lisp instead of xml, or?
>
> Yeah. Though... XML is important enough nowadays that Emacs really
> ought to be able to parse it with good performance. If this means
> linking to an XML library written in C, then IMO it would be a good
> idea.
But parsing xml can't be as fast as just reading elisp code, or? But
maybe the speed difference would be negligable, I do not know.
next prev parent reply other threads:[~2008-03-12 23:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.8709.1205244459.18990.help-gnu-emacs@gnu.org>
2008-03-11 15:56 ` code completion Richard G Riley
2008-03-11 19:50 ` Eli Zaretskii
2008-03-11 21:07 ` Lennart Borgman (gmail)
2008-03-12 4:14 ` Eli Zaretskii
[not found] ` <mailman.8726.1205269686.18990.help-gnu-emacs@gnu.org>
2008-03-11 21:15 ` Richard G Riley
2008-03-12 9:56 ` Arne Schmitz
2008-03-12 19:37 ` Óscar Fuentes
[not found] ` <mailman.8785.1205350636.18990.help-gnu-emacs@gnu.org>
2008-03-12 19:51 ` Pascal Bourguignon
2008-03-12 20:58 ` Tom Tromey
2008-03-12 22:22 ` Lennart Borgman (gmail)
2008-03-12 21:35 ` Tom Tromey
2008-03-12 23:17 ` Lennart Borgman (gmail) [this message]
2008-03-12 23:24 ` Jason Rumney
2008-03-13 0:14 ` Óscar Fuentes
2008-03-12 21:40 ` Óscar Fuentes
[not found] ` <mailman.8721.1205265045.18990.help-gnu-emacs@gnu.org>
2008-03-11 21:05 ` Richard G Riley
2008-03-12 4:19 ` Eli Zaretskii
[not found] ` <mailman.8740.1205295602.18990.help-gnu-emacs@gnu.org>
2008-03-12 4:55 ` Richard G Riley
2008-03-12 9:11 ` Bastien Guerry
2008-03-12 11:17 ` Richard G Riley
2008-03-12 12:06 ` Bastien
2008-03-12 12:29 ` Richard G Riley
2008-03-12 13:07 ` Bastien Guerry
2008-03-12 16:06 ` Richard G Riley
2008-03-11 14:08 Alain Muls
2008-03-11 19:36 ` Eli Zaretskii
2008-03-12 9:06 ` Bastien
[not found] ` <mailman.8747.1205313317.18990.help-gnu-emacs@gnu.org>
2008-03-12 11:23 ` Richard G Riley
2008-03-12 12:07 ` Bastien Guerry
2008-03-12 12:30 ` Richard G Riley
2008-03-12 13:10 ` Bastien Guerry
[not found] <mailman.3235.1151043305.9609.help-gnu-emacs@gnu.org>
2006-06-23 18:45 ` Code completion Boof
2006-06-23 20:03 ` Thorsten Bonow
2006-06-24 23:45 ` Jorge Peixoto de Morais Neto
-- strict thread matches above, loose matches on Subject: below --
2006-06-23 6:14 Jorge Peixoto de Morais Neto
2006-06-23 20:34 ` Noah Slater
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=47D8648E.4010100@gmail.com \
--to=lennart.borgman@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=tromey@redhat.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).