John Spikowski wrote:Personally I think it's a big mistake not to allow C includes. (with the new C emitter) Having to translate libraries so FB can use them is a pain to maintain.
It is both a mistake to do and to don't.
To do because from a birds eye it is the ultimate solution. (as defined as without changes to the calling code compared to the FB header)
To don't because many have tried and failed, or produced unworkable solutions.
This means you can never fully rule out "DO", since somebody might still come up with a workable solution. Any "half way" solution essentially turns the calling code into C with only minor syntax differences.
This discussion doesn't only happen here, it also rages in e.g. FPC.
So I think the current position of don't, till a working patch gets submitted is the most productive. If people with an academic interest come up with something, the stance can always change. However this is not routine Compilers 101 work.
I still think FPC->FB header translation is the way :_)