Hello,

> having separate branches or different subprojects to support different 
> versions of the standard

I don't quite see the point of having different compilers for different version 
of the standard.

Since C11 covers and fixes C99, C99 is "included" in C99.

I know that C99 is already a first step for C11 support, let's do it first then.

Making sure that C99 support is granted for version 0.9.28 or 1.0.0 ?

Some useful docs on C99's features :

https://www.open-std.org/jtc1/sc22/wg14/www/C99RationaleV5.10.pdf

https://gcc.gnu.org/projects/c-status.html#c99

https://en.cppreference.com/w/c/99.html

https://en.wikipedia.org/wiki/C_data_types

https://github.com/AnthonyCalandra/modern-c-features or 
https://github.com/AnthonyCalandra/modern-cpp-features

https://docs.oracle.com/cd/E19422-01/819-3688/c99.app.html

https://www.ibm.com/docs/en/xl-c-aix/13.1.0?topic=extensions-c99-features

https://www.ibm.com/docs/en/i/7.5.0?topic=extensions-standard-c-library-functions-table-by-name

https://pubs.opengroup.org/onlinepubs/009604499/utilities/c99.html : CLI syntax 
?

https://medium.com/@pauljlucas/obscure-c99-array-features-cf5ecc71bbd2

Regards


----- Mail d'origine -----
De: Страхиња Радић <[email protected]>
À: [email protected]
Envoyé: Sun, 10 Aug 2025 14:26:08 +0200 (CEST)
Objet: Re: [Tinycc-devel] Re : Re:   Re : Re:  VERSION Number 1.0

Дана 25/08/10 02:10PM, [email protected] написа:
> Let's say C99 should be covered indeed, 25 years in the making, but
> C11 shouldn't be ditched.

That wasn't what I proposed, but that the current focus should be full
C99 compliance. There is a number of ways how the future support for
other versions of C standard after full C99 compliance is achieved
could be handled. For example, having separate branches or different
subprojects to support different versions of the standard.

_______________________________________________
Tinycc-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel


_______________________________________________
Tinycc-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Reply via email to