I would appreciate if you revert the changes in mob, beginning with https://repo.or.cz/tinycc.git/commit/8b58a07b95a637e6d9060b4c26bc0f2e7758f1a4
On 21.11.2026 20:08, Christopher Bazley wrote:
Before I do that, I would welcome grischka's view, as well as those of other TinyCC developers, on whether support for _Optional can remain on mob.
I didn't look much into newer patches for some time however from first glance those series by Christopher didn't look unreasonable to me even if seemingly addressing somewhat "exotic" features for my taste, for some parts. I also don't usually care much about those new C123xy standard inventions because after all we didn't vote for them and were not invited to either. Also I guess I got used to use or not to use null pointers for just too long that I could still see what problems anyone possibly could have with that. I'd maybe just not let a program ever grow to the point where it becomes impossible to see through its logic without the compiler's help and a new keyword. Also I think we strongly do avoid practices of paranoid coding in tinycc, so should tinycc provide new keywords in order to support paranoid practices elsewhere? Interesting question... Anyway I do however appreciate seeing someone at some standard committee explicitly lobbying for tinycc as a fast compiler. I noticed that almost all of our VT_XXX type bits were used up by now, so at some point we might be forced to do something about that ;) -- gr
If a revert is the consensus opinion, I would like to ensure that independent bug fixes and C23 improvements are preserved. Thanks, Christopher
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
