This is the mail archive of the
mailing list for the GCC project.
Re: Proposed plugin API for GCC
- From: ludovic dot courtes at inria dot fr (Ludovic Courtès)
- To: gcc at gcc dot gnu dot org
- Date: Fri, 30 Mar 2012 10:23:16 +0200
- Subject: Re: Proposed plugin API for GCC
- References: <1333054687.31165.65.camel@surprise>
David Malcolm <firstname.lastname@example.org> skribis:
> How do other plugin authors feel about the API?
I think this approach would lead to a duplication of each GCC API.
The needs of plug-ins cannot be anticipated; artificially restricting
what plug-ins can do is likely to hinder wider extension of GCC.
As an example, when Emacs was written, probably nobody expected that
email and IRC clients would be written in it; likewise, probably most of
the projects at <http://llvm.org/ProjectsWithLLVM/> were not anticipated.
What about sticking to the current âAPIâ instead, and explicitly marking
as internal those parts that core developers know are still in flux?
For instance, I would expect a large subset of <tree.h> and <cgraph.h>
to be stable (itâs been the case in my experience between 4.5 and 4.7.)
The rest can be tagged with a special convention (for instance, an âi_â
prefix), to make it clear that itâs only meant for internal consumption.