Generating export statements

[amitmurthy]

Can wrap_c.init() take in an additional callback function which can be used to determine if a function should also be exported and the corresponding export statement generated?

[amitmurthy]

Actually, not just functions but enum consts too.

[ihnorton]

Good point. I didn't think about this very much yet, for smaller libraries it makes a lot of sense.

What do you think about having a BOOL all/none to export everything in a library? The reason I say this is that, if you are going to manually enumerate some subset in the wrap driver, then could just do that in the library's "main" Julia file (the import wrapper).

[amitmurthy]

Works for me. I am trying to wrap libCURL and it has a ton on enums. A bool flag is fine or another option is to specify a separate output file only for the export statements. I can then opt to "include" this exports-only file in my main module if I want to export everything or just ignore it.

Either model works, but a bool for now is probably good enough.

[ihnorton]

The "wrapcontext" variable has a field called cache_wrapped which contains all of the names that have been generated. Will this suffice for generating exports in the driver code?

[amitmurthy]

I think it is missing the enum definitions currently. Those consts need to be exported too.

[ihnorton]

@amitmurthy this definitely works for enums now, although I'm not exactly sure where I fixed it! Please re-open if needed in future.