David Malcolm <dmalc...@redhat.com> writes: > I had a go at writing a possible plugin API for GCC, and porting parts > of my python plugin to it: > http://git.fedorahosted.org/git/?p=gcc-python-plugin.git;a=commitdiff;h=36a0d6a45473c39db550915f8419a794f2f5653e
Seems like a good start. > I initially attempted an underscore_based_naming_convention but quickly > found it difficult to get concise function names, so I switched to a > CamelCaseBased_NamingConvention with an underscore separating a notional > namespace element from a secondary element, which saved plenty of space. > The different naming convention also serves to highlight that this is > *not* part of GCC's internals. Predictably, I don't care for the names. I would recommend grouping functions by category, and making each category be a struct with a set of function pointers. That will give you a namespace, and will greatly reduce the number of external names in the API. Ian
