public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mrs@windriver.com>
To: gcc@gcc.gnu.org, ttn@gnu.org
Subject: Re: C/C++ front-end extension a la SWIG?
Date: Wed, 05 Jul 2000 17:48:00 -0000	[thread overview]
Message-ID: <200007060047.RAA11284@kankakee.wrs.com> (raw)

> Date: Wed, 28 Jun 2000 17:21:39 -0700
> From: thi <ttn@revel.glug.org>

> i understand gcc backend is unlikely to be librarified (from reading
> the thread: http://gcc.gnu.org/ml/gcc/2000-01/msg00257.html ), but
> how about the C/C++ front-end?  what i'd like is to be able to
> integrate guile w/ the parser so as to be able to map .h
> declarations to make glue code.

> this is similar to what swig ( http://www.swig.org ) currently does,
> but i'm thinking it would be better to use the widely used and
> tested parser from gcc than the swig parser, which does not grok
> many C++isms.

> does this make sense?  is there anyone working on something like
> this?  would this kind of work be harmful to the free software
> community?  is there a better approach (that allows me to use the
> gcc parser)?

How about this, we settle on something like swig, and have gcc/g++
generate swig friendly data into a file, and then have swig read that
file and generate what it needs to.  The xref stuff in the compiler
might be worth dusting off, it might be kinda like what one wants
(I've not thought about this much, I've not studied swig).  Should be
fairly low maintenance, can be used/reused for other languages
(GNU Fortran/GNU Ada...)

             reply	other threads:[~2000-07-05 17:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-05 17:48 Mike Stump [this message]
2000-07-06 11:19 ` Laurent Guerby
2000-07-10 17:17 ` thi
  -- strict thread matches above, loose matches on Subject: below --
2000-06-28 17:24 thi
2000-06-29  0:45 ` Martin v. Loewis
2000-06-29  1:14   ` Mark Mitchell
2000-06-29  6:25     ` Daniel Berlin
2000-06-29 10:36       ` Mark Mitchell
2000-06-29 10:54         ` thi
2000-06-29 11:29           ` Mark Mitchell
2000-06-29  8:48   ` thi
2000-06-29 11:58     ` Andi Kleen
2000-06-29 12:22       ` Daniel Berlin
2000-06-29 12:24         ` Andi Kleen
2000-06-29 12:28           ` Daniel Berlin
2000-06-29 13:43     ` Martin v. Loewis
2000-06-29 15:09       ` Daniel Berlin

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=200007060047.RAA11284@kankakee.wrs.com \
    --to=mrs@windriver.com \
    --cc=gcc@gcc.gnu.org \
    --cc=ttn@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.
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).