>>>>> "Sean" == Sean Callanan <spy...@cs.sunysb.edu> writes:
>> (3) The -fplugin-arg argument is one way to do arguments. We do it as
>> -ftree-plugin=/path/to/plugin.so:arg=value:arg=value:...
Benjamin> I'm a little worried about the colon separator. Windows file
Benjamin> paths may legally have colons. Is there some separator
Benjamin> character (semicolon?) which is not part of a path on any
Benjamin> platform? Perhaps we shouldn't worry about it since
Benjamin> -rdynamic doesn't work on Windows anyway.
Sean> Agreed. OS X paths can include semicolons, though. This is
Sean> something we need to think about.
Rather than invent a new quoting syntax, why not just split the
arguments up? If each a plugin has a name, you could use that name in
subsequent -f arguments. E.g., if the name of the plugin in
"plugin.so" is "foo", perhaps:
-fplugin=/path/to/plugin.so -ffoo-arg1=value1 -ffoo-arg2=value2
The actual spelling could be "-fplugin-$NAME-arg" if you think the
above is too likely to clash with already existing (or future)
argument names.
I wanted to mention this idea, but since I know this is an area prone
to bikeshedding I don't intend to argue strongly for it.
Tom
