Re: [Tinycc-devel] bug in preprocessor

2024-01-19 Thread Fred van Kempen via Tinycc-devel
> To put some text after #endif on the same line, this used to be customary> in > K age, wasn't it?Yes, and that has evolved into using comment markers > there, likein #endif    /*foo*/ for example. > There are K sources still valuable today and it is really useful that > Tinycc is capable

Re: [Tinycc-devel] bug in preprocessor

2024-01-19 Thread Fred van Kempen via Tinycc-devel
> It also compiles, with a warning, both with GCC (13.2.0) and Clang > (15.0.7).It should generate a warning, yes. Fred ___ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Re: [Tinycc-devel] bug in preprocessor

2024-01-19 Thread Harald Arnesen via Tinycc-devel
Fred van Kempen via Tinycc-devel [18/01/2024 21.35]: This: #include #include int main(int argc, char **argv) { #ifdef FOO     printf("Foo: %s\n", argv[0]); #endif  bar     return argc; } should not compile, for obvious reasons, but it does.. Using 0.28rc. It also compiles, with a

Re: [Tinycc-devel] bug report / preprocessor / string literals

2006-02-13 Thread Bernhard Fischer
On Fri, Jan 27, 2006 at 12:16:20PM +0100, [EMAIL PROTECTED] wrote: Hi @, There seems to be a bug in the preprocessor when using # to create string literals. The following source ... #define printxml(xml) printf(#xml) #define nl printf(\n) int main() { printxml( html /html );