This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Proposed plugin API for GCC

From: Romain Geissler <romain dot geissler at gmail dot com>
To: David Malcolm <dmalcolm at redhat dot com>
Cc: Basile Starynkevitch <basile at starynkevitch dot net>, gcc at gcc dot gnu dot org
Date: Sat, 31 Mar 2012 11:09:49 +0200
Subject: Re: Proposed plugin API for GCC
References: <1333054687.31165.65.camel@surprise> <CAFiYyc35AGhXUV7Q8hff=uXxyusoBezt+E_+goZwgOe=Le3Zmg@mail.gmail.com> <20120330130854.GB15238@ours.starynkevitch.net> <1333154753.2447.44.camel@surprise>

Hi

Le 31 mars 2012 à 02:45, David Malcolm a écrit :

> Here's another proposal then: actually use GObject introspection -
> provide a GObject-based API to GCC.
> 
> In this approach, GCC would gain a dependency on glib and gobject, and
> expose its API via a .gir file.

I don't think adding huge dependencies only for plugins is welcomed.
A C/C++ API is far enough and quite simple to use. People that are willing
to use Gobject or anyhting else are free to wrap the wrappers.

By the way, your proposed API is promising (through i also love
CamelCasing and i'd prefered a C++ API).

Cheers

Romain Geissler

References:
- Proposed plugin API for GCC
  - From: David Malcolm
- Re: Proposed plugin API for GCC
  - From: Richard Guenther
- Re: Proposed plugin API for GCC
  - From: Basile Starynkevitch
- Re: Proposed plugin API for GCC
  - From: David Malcolm

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]