You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could resolve the condition when we generate the headers: the value of EXTENDED would have to be known when we generate the headers. This is far by the simpler option, and should probably be the default
We could delay the decision, and generate Haskell code that relies on the same condition:
If we want to support this at all, we probably only want to support it in a very minimal fashion, because libclang itself does not support this mode; so if for example we wanted to query libclang for the offsets of the fields inside structs, if there is CPP involved, we'd have to run libclang for each possible CPP permutation. Marking this as a low-priority enhancement for now.
Suppose we have a C header such as
we have two ways to proceed:
EXTENDED
would have to be known when we generate the headers. This is far by the simpler option, and should probably be the defaultThe text was updated successfully, but these errors were encountered: