> On 15.11.2014, at 20:53, stepharo <[email protected]> wrote: > > > On 15/11/14 12:37, Max Leske wrote: >> I got a bit frustrated and ended up searching the source for >> ‘[\w]opt[[:upper]]’ to find all NativeBoost options. Some of those options >> are in fact undocumented: >> >> optMayGC >> optProxyLabels >> optCdecl >> optReturnNullAsNil >> optStdcall >> optNonMovable >> optReserveCallgateSpace >> optDebug >> optNoAlignment >> optEmitCall >> optNoCleanup >> optCheckFailOnEveryArgument >> optStringOrNull >> WinUnicode >> >> NBFFICallout>>defaultOptions documents most options but refers to >> NBFFICallout>>allOptions, wich does not exist. Most of the above options can >> be considered internal, I guess, but the one option I needed >> (‘optStringOrNull’) isn’t documented anywhere. I had to step through the >> execution to find out why my function call wasn’t working (because I was >> trying to use ‘optCoerceNilToNull’ and didn’t know that strings need a >> special option). >> >> I’d be very thankful if these options would be included in the documentation. > Which documentation? There is one?
Well, there’s a bit of documentation on Google code and then there’s NBFFICallout class>>defaultOptions, which has some comments. That’s it basically. > And yes this pisses me off. > >> >> Note: ‘WinUnicode’ is used by the Windows code in a couple of places, even >> though the option name is not valid, according to >> NBNativeCodeGen>>parseOptions: >> >> Cheers, >> Max >> > >
