Hi David, thanks for asking, since i consider C11 and C-language features overall highly critical.
> Why C11 and not just C99 ... > That a source code base is "tied" to a C revision (your __thread example) There is a mis-understanding of yours: in fact i tried to AVOID C11, in particular __thread extension by rolling back ISC/bind9 package version in this case for support with tinycc, which did NOT need __thread for NPTL then. It's just an exemplary case, since this system is driving DNS infrastructure globally, and latest versions of it got destabilized since 2022 by C11; NOT improved, C11 destabilized bind9 and C-toolchain portability got infringed. Don't ask me who made those decisions, it wasn't me. > The C "standard" is a joke It wasn't until another such "improvement" of C-lang appeared, that i avoided, which was the C11 #generic macro nonsense inside linux5-kernel. Don't ask me why Linux accepted this, instead of remaining conservative close to C90 which they did for decades. There's too various POSIX revisions at stake, beyond the scope of tinycc-devel. With regards to tinycc, that follows a pragmatic approach, which so far had proven appropriate to re-integrate a complete(!) and fully capable Tinycc/Linux operating system here - WITHOUT __thread and various other such "improvements". You may want to have a look at the documentation i posted online with my tiny test site http://tinyfront.mooo.com/docs.html where i'm re-iterating over "acceptance criteria" and standards compliance. Too the footnote section might provide some insight into what I REALLY think about this. But i am not a tinycc developer myself, i've been occupied with menial system-integration tasks "only" The only "improvement" of C11 standard i am aware of so far is _complex extension is considered optional with it, while C99 considered it mandatory. Tinycc hasn't got _complex extension either. You may consider this C11 then if you wish. The only "improvement" of C11 standard i am aware of so far is _complex extension is considered optional with it, while C99 considered it mandatory. Tinycc hasn't got _complex extension either. You may consider this C11 then if you wish. > I'm really considering to switch to something just as "old" but at least > consistent : pascal. Pascal language is none of my business, and i do not see any benefit of it over ISO/ANSI C language. For that matter i've seen alot of crap written in Python, which is praised for it's strictness, simplicity whatever. I rather avoid Python and similar since it's not covered by ISO/ANSI/IEEE standardization at all. > Not like the usual mess of header inclusions and guards, macros targeting > certain compiler version and vendor It's more of a question who is writing software with any language, than the language chosen. And conservative C remains my favorite. Meanwhile i've finished the teTeX-3 port to tinycc/linux, that is GNU/C90 whatever, removed some unnecessary c++ codepath from it, hacked the autotools junk to pass autoreconf again. A voila, there's TeX and PDF support back on board. Michael Ackermann On 2026-02-13 22:12, [email protected] wrote: > Thank for the insight. > > Why C11 and not just C99 ? > > Because C11 provided enough justifiable features and not being 27 years old. > > Like name struct initializer. > > I don't want to mess with C89. > > The C "standard" is a joke that borrow "ideas" from other languages to try to > stay "relevant".
signature.asc
Description: Digital signature
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
