Christoffer Lerno
Christoffer Lerno
Not all of those are libc, but rather gnu additions or posix.
That latter is part of the size checking.
Well, this is just the parser information. If you want something to consume for LSP, it should presumably go through analysis too, but at that point some of the data...
Yes, but if we think about wanting to create mappings. For example, consider `int x = FOO` Now in the AST pass before semantic checking this is just "some constant...
I would not use the c3c parser, since you want something more lenient for an LSP: it should be caching information and work well with incomplete data and such.
There is a related feature, `@weak` which should work with this but doesn't. I need to reexamine its use.
I'm still working on this. Basically Windows does not have proper weak symbols. Instead they have linkonce and emulating weak using comdat. Unfortunately, if you have a regular symbol it...
We can set all functions to use comdat on Windows? That wouldn't necessarily work with other C functions though.
In general macros should be fewer because they are worse for ABI compatibility.
@patroclos doesn't `$defined(a < a)` work?