OFP embedded pre-processor directives

[Synide]

Question.

Has anyone scoped the extent of the capabilities of the embedded pre-processor in OFP?

I ask because... as one can use the '#include' directive... one maybe able to use the '#import' directive and exffectively expose binary compiled .dlls, type-libraries etc, etc. as callable functions within OFP?!

This thought stems from a post I saw regarding implementing advanced math functionality in OFP. But, if the above could be done... then we'd just be able to grab third party libraries of useful functions... and.. hmmmm, oh this is probably all just a silly left-brain thought...
Anyway, thought I'd ask...

Cheers, Simon.
sbeetham@yahoo.com

[CrashDome]

Only #include will work and only in add-on configs (which I do not know too much about).

If you try and use #include in the description.ext file for a mission, it will only grab from the OFP default directory not the mission folder/pbo file - and it must fit OFP standards and conventions (slightly different from C or C++)

http://www.flashpoint1985.com/cgi-bin/ikonboard311/ikonboard.cgi?s=d3e14955bd91c93c3515808919544a79;act=ST;f=7;t=25735

[Synide]

Thanks for that... I gave up trying that a couple of days ago... should have closed this topic...

Cheers.