3 ms·
> I had no idea the compiler needed external tooling, I thought it was self sufficient. It used to be self-sufficient. But, we had to give up on our linker bec
by WalterBright 3y ago
> I had no idea the compiler needed external tooling, I thought it was self sufficient.
It used to be self-sufficient. But, we had to give up on our linker because we didn't have the staff to keep a linker up to date, and decided to stop chasing windmills and just use what was available. ImportC, in order to work, needs a preprocessor. We do have our own Standard compliant preprocessor, but it had a major problem. All the C preprocessors predefine a ton of macros (cpp predefines up to 400 macros). Different combinations of compiler switches turn on or off those predefines in poorly and usually undocumented ways. It differs from preprocessor to preprocessor, and was a hopeless nightmare.
So, ImportC uses the C preprocessor of the associated C compiler, and that works like a champ. The downside is you'll need to have that preprocessor installed and on the path.
- Alifatisk 3y agoI appreciate the explanation, that makes total sense. The burden to maintain such a preprocessor doesn’t seem that rewarding compared to using existing ones.