L.s.
You know I want to write 4tH in the most vanilla and pedantic C possible. That is a challenge, because both may not lead to the same code. Still, some time ago I got some Lint patches from François Perrad and I decided they were useful to harden 4tH.
There are two I decided against. First, including the .h file with self contained .c files. Yes, you could check if the prototype matches, but that is my work, not the compilers. Second, flagging all functions in an application program as "static". That means that functions cannot be exported, but that is pretty futile in an application program and just adds noise. Tell me I'm wrong here and I'll apply them.
But there was something else. I hate applying lots of code patches to a working program, since you never know what goes wrong. Sure, I checked and double checked, but there's always that nagging little voice, saying you might have overseen something.
So, first I have to see whether the code still compiles with Coherent and Turbo C (the most difficult ones) and second, I have to gain trust again in the program by just using it. I will do that shortly.
I still have some ideas concerning some new opcodes, but I can't guarantee they will make it in the next release. If you want to inspect the code yourself, it is in SVN now (Sourceforge had some trouble 19 Feb 2017).
Of course, Francois got the proper credits for his very useful patches.
Hans Bezemer