From: Tom Tromey <tromey@redhat.com>
To: Dodji Seketeli <dodji@redhat.com>
Cc: Chris Moller <cmoller@redhat.com>,
Sergio Durigan Junior <sergiodj@redhat.com>,
Project Archer <archer@sourceware.org>
Subject: Re: Parser rewritting
Date: Thu, 08 Apr 2010 19:28:00 -0000 [thread overview]
Message-ID: <m38w8xrbf6.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100404084952.GK20524@redhat.com> (Dodji Seketeli's message of "Sun, 4 Apr 2010 10:49:52 +0200")
>>>>> "Dodji" == Dodji Seketeli <dodji@redhat.com> writes:
Dodji> Would the copyright assignment requirements prevent us from trying to
Dodji> reuse, say, Clang? Maybe one could think about providing a C api on top
Dodji> of Clang and consider Clang as an external dependency?
This can be done, after all, we do it with Python :)
A new external dependency always causes trouble, though. Look through
the archives to see the discussions around expat, python, and libiconv.
A required external dependency will be trouble.
Anyway, I suspect the impedance mismatch problem holds equally for clang.
It is probably worth verifying that.
Dodji> I understand that this minimal parser is meant to stay simple, e.g. no
Dodji> preprocessing support, very minimal error reporting if any at all, no
Dodji> semantic analysis etc, but still, if we can't re-use Clang, then would
Dodji> it be possible to devise this new "minimal parser" as an independant,
Dodji> reusable library with its own dejagnu-free testsuite?
Dodji> Maybe other projects might be interested in using (and extending)
Dodji> something like that.
I'm not opposed to this but I don't want to slow down our progress to
make a library.
Tom
next prev parent reply other threads:[~2010-04-08 19:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 18:46 Sergio Durigan Junior
2010-03-30 19:05 ` Chris Moller
2010-03-30 21:12 ` Tom Tromey
2010-04-04 8:50 ` Dodji Seketeli
2010-04-08 19:28 ` Tom Tromey [this message]
2010-04-10 22:05 ` Jim Blandy
2010-04-10 22:11 ` Jim Blandy
2010-03-30 21:18 ` Tom Tromey
2010-03-30 22:20 ` Keith Seitz
2010-03-30 22:59 ` Tom Tromey
2010-03-31 2:01 ` Matt Rice
2010-04-02 1:50 ` Chris Moller
2010-04-08 19:21 ` Tom Tromey
2010-04-08 20:21 ` Chris Moller
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=m38w8xrbf6.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@sourceware.org \
--cc=cmoller@redhat.com \
--cc=dodji@redhat.com \
--cc=sergiodj@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).