Hi, I want to use tcc in a cross-platform project which primarily targets Windows. I have used tcc successfully a couple of years ago so I have some familiarity with the code. I find the code very difficult to work with because of the technique of including .c files. This prevents my IDE and debugger from working properly. Even with the IDE aside, it is pretty difficult to navigate the code when so much of it is in one file.
I would like to split the code into multiple files, and separate as much as possible the OS specific code so that improving the Windows support doesn't increase the spaghetti of #ifdefs. I am using the library API to tcc and it needs some improvement too so that all of the compiler options can be set through the API and so that multiple TCCState objects can exist at once. sqlite is an interesting model for how to have code split across many files for development, but they support a single amalgamated source file (which is automatically generated). This seems like a good model for tcc because it would make development easier, but also keep it easy to integrate tcc into larger projects as a component. Anyway, the bottom line is, if I do this, what are my chances of getting the changes accepted into the mainline? Does anyone else have any input on how they would like to see the code structured? Regards, K1w1.
_______________________________________________ Tinycc-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/tinycc-devel
