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: Plugin API Comments (was Re: GCC Plug-in Framework ready to port)

From: Sean Callanan <spyffe at cs dot sunysb dot edu>
To: Taras Glek <tglek at mozilla dot com>
Cc: gcc at gcc dot gnu dot org
Date: Mon, 2 Feb 2009 19:54:58 -0500
Subject: Re: Plugin API Comments (was Re: GCC Plug-in Framework ready to port)
References: <m3iqnwwqrl.fsf@google.com> <EFC35277-A978-4B6E-9F06-DC56C1409B99@cs.sunysb.edu> <b798aad50901310511o3884804fs2f5392e509ab14df@mail.gmail.com> <D14E0693-7B34-4E6A-9405-E35BBC98A897@cs.sunysb.edu> <4987464E.3070406@smedbergs.us> <7A18A5B8-0C5E-4961-892A-3B7060FCD091@cs.sunysb.edu> <49879111.7080902@mozilla.com>

Taras,

On Feb 2, 2009, at 7:34 PM, Taras Glek wrote:

Regarding versions: I think it's crazy to be passing a version in every single function call. The plugin should check the gcc version it is being loaded into on startup and bail if it doesn't match.

Since you and Diego seem to be of one mind on this, we can just strip versions. It might be useful to have an API inside GCC for picking apart version_string for purposes of comparison, but we can add that to "Nice to have" since it is in no way plugin-specific.

I'll go ahead and strip the hook versioning API out of the draft.

Sean

References:
- Plugin API Comments (was Re: GCC Plug-in Framework ready to port)
  - From: Sean Callanan
- Re: Plugin API Comments (was Re: GCC Plug-in Framework ready to port)
  - From: Benjamin Smedberg
- Re: Plugin API Comments (was Re: GCC Plug-in Framework ready to port)
  - From: Sean Callanan
- Re: Plugin API Comments (was Re: GCC Plug-in Framework ready to port)
  - From: Taras Glek

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