[Solved] Re: Is importC ready?

[Paulo Pinto]

On Thursday, 18 November 2021 at 04:38:36 UTC, bachmeier wrote:
> On Monday, 15 November 2021 at 21:29:53 UTC, bachmeier wrote:
>> On Tuesday, 9 November 2021 at 16:41:04 UTC, bachmeier wrote:
>>> [...]
>>
>> There's a solution for this. Buried in a recent post on This 
>> Week in D, there's [a link to a list of 
>> fixes](https://raw.githubusercontent.com/ibuclaw/importC/main/src/keywords.c.in). That plus `#define __builtin_isnan isnan` allows my C file and many others to compile with LDC. Some files that compile with LDC do not compile with DMD. I'm still having trouble with `__builtin_isfinite` errors. I thought `#define __builtin_isfinite isfinite` would work, but it doesn't.
>>
>> Once I understand this better, I will update the issue I 
>> created.
>
> Giving up on this experiment. It's much easier/faster to wrap 
> what I need and forget about the rest. Solve one problem and 
> you get three new compiler error messages. Eventually I run 
> into something I can't fix, so I move on to a new file, and 
> it's the same thing. It's hopeless without a complete 
> implementation or workaround for all of the GCC compiler 
> extensions. I honestly have no idea why they pretend C is 
> standardized.

Because the real truth is that with pure ISO C, there are plenty 
of stuff that would only be possible with Assembly, and place C 
at the same spot as other high level languages, and we cannot 
damage C's reputation as the systems programming language, now 
can we?