For me, the biggest draw that keeps me coming back and using TCC is that the code is simplified with only what is needed to compile the code. It's specifically the _lack_ of features that makes TCC a daily driver for me on the unusual platforms/uses I use it with. I know it may sound silly, but I think its success is crucially dependent on the default build size being very small, much more than on any features it could offer. And beyond that - keeping the ideas and concepts expressed in the code down to what they need to be to "get the job done" - without throwing in extra logic to enable/disable features, keeping the code readable (well, as readable as a codebase this inscrutable can be).
Typically, when I'm using TCC, it's because I'm already in a weird position, targeting an unusual corner case, and almost universally in those cases, brevity always trump user-friendliness, value-wise. On Sun, May 12, 2024 at 5:27 AM Vincent Lefevre <vinc...@vinc17.net> wrote: > > On 2024-05-12 07:20:13 +0000, avih via Tinycc-devel wrote: > > Personally I don't think this is required, but I don't pretend to > > represent the tinycc maintainers' opinion. If it is added, however, > > then the following should probably be taken into account: > > > > - This mostly works, but it won't work on all terminals, for instance > > the original DEC VT100 has bold but doesn't have colors. > > > > - It's probably better to support disabling it by means other than > > piping stderr into "cat" (so that stdout is not a tty). I.e. using > > an option, probably with value always/never/auto. Preferably it > > should also respect NO_COLOR by default. see https://no-color.org/ . > > In any case, it should automatically detect whether colors are > supported by the terminal (something similar to what "tput colors" > does), something that GCC fails to do. > > -- > Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> > 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> > Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) > > _______________________________________________ > Tinycc-devel mailing list > Tinycc-devel@nongnu.org > https://lists.nongnu.org/mailman/listinfo/tinycc-devel _______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
