On 8/9/2025 5:16 AM, [email protected] wrote:
1- What should be present in the 1.0.0 release ? Full C99 or C11 support ? C11 is safer and more "up to date" :
Neither? My conclusion from reading the whitepaper your suggested, "C11: A New C Standard Aiming at Safer Programming".
Michael's suggestion of basing upon tinyfront seems best.
4- Write tickets in a VSC like GitHub (or Savannah, provided everyone stick to it).
What is a VSC?
5- Set a roadmap and deliverables with expected feature support and bug fixes, not necessarily deadlines (0.9.27 has been out for a while). 6- Set an easy to use cross platform working environnent (unzip and play) for volunteers to debug and code. 7- Get volunteers to take charge of tickets and carry out their holy duty. 8- Get their job peer reviewed, merge their commits from separate development branch into the main one (depending on the workflow used) :
An exciting effort, but shall we first apply for and win a large grant, in order to cover the cost of the extra administrative and marketing effort? ;-)
Meanwhile, continue processing bug fixes as pull requests to github repo? Robin _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
