reserved identifier violation about limine HOT 6 CLOSED

Thanks for reporting the issue. This is indeed a problem, but one that plagues C codebases all throughout, not just the Limine project...

I have changed the include guard macro in limine.h as that is the most important one since it's the exposed header, and changed Flanterm to also not use reserved identifiers for its include guard macros. I also used -isystem instead of -I for the freestanding-headers includes (as it should be since they are libc-replacement headers).

Other than that, it hardly matters since the reserved identifiers used are unlikely to cause conflicts, but if there are any issues at any point stemming from reserved identifier conflicts I'll fix those on a case-by-case basis.

from limine.

Thanks for your adjustment of an affected include guard.

💭 How do you think about to avoid any more that this software depends on undefined behaviour?

from limine.

I am not quite sure what you mean, but beyond the use of reserved identifiers in some places, if there are other instances of invoked undefined behaviour, please let me know.

from limine.

💭 Would you become interested to use a development tool like “clang-tidy” for corresponding source code adjustments?

from limine.

That's not what I asked. I will also stop replying to you as well, given it is likely either some bot or AI talking, not a real human.

from limine.

That's not what I asked.

👀 We know that some update candidates are still remaining.

I will also stop replying to you as well, given it is likely either some bot or AI talking, not a real human.

Please reconsider such a view.
🔮 Can I convince you anyhow about further improvement possibilities?

from limine.