@thephd @fay59

> You, the vendor, parse things based on -std=... or /std:..., like everyone else.

So... basically if you have a C2y libc, you need an #if __STDC_VERSION__ gate around your printf declaration with different symbol versioning, to make sure that programs compiled with -std=C2y will fail to load on old systems whose libc doesn't support C2y, but still allow programs built with -std=C11 to work there?

@gamingonlinux the fact that is inside a "#if 0" and clearly a relict from early development makes it a bit less funny though.

oh I see, it's mad about the missing semicolon (which isn't an error, because that #if is currently false)

and is expressing it the only way it knows how, with nonsensical indentation

@millenomi @chbeer I wish we had a `not` identifier in Swift (I think C(++)’s iso646.h has that, for platforms where != caused encoding problems), that'd just stand out more.

And yeah, sometimes an #if is just for an obscure platform, and it just makes sense to front-load the code that's relevant for 90% of your devs.

Though generally I try to wrap stuff like that in functions or platform-specific classes that implement a shared interface. Then only object-creation is platform-specific.

#Meanwhile...

#PSiReN-Group #Stills #ComesComplete with #ZeroReports and #TootSuite; #PoweredBy: #FloofsAndSparkles...

Have we #HadEnoughRainbows yet, #Today...? With #PiratePower...

And, #IncreasedPerformance and #Circulation in #TheYearOfTheWoodenDragon...?

#TheRules:

1: #KnowTheRules
2: #RememberTheRules
3: #TryNotToKillAnyone

And, #DontForget... #MaskUp...

#BTW: #IF you're #Still #NotQuiteSure, #CantQuiteRemember (or #JustDontKnow) how a #FederationWorks...

#LookITUp | #DogsCanLookUp

​​​​​ | ​​​​

@mcc

I assume by "erase" you mean "suppress compile".

If so then yes, "#if false" works perfectly well for what you want.

C# "#if" is really a hybrid of C "#if" and "#ifdef". Any defined symbol evaluates to boolean true, regardless of what it's defined to, and you can do boolean math on them, e.g.
#if A || B

I use variations on "#if false" and "#if true" a lot when I'm debugging code I want to be conditionally compiled under some circumstances/targets.

@mcc wow that documentation really doesn’t help

Running an experiment:
#if false appears to remove the code
#if true appears to keep the code
#define false is forbidden because false is a keyword not an identifier

Which all suggests to me that true/false are special in #if, but that page sure doesn’t say that…

@mcc

#if false
Console.WriteLine("Hello false");
#endif
#if true
Console.WriteLine("Hello true");
#endif

printed hello true.

adding a DefineConstants for false
1. wasn't an error
2. still only printed "hello true"

@mcc I've done #if false / #if true things before and it seemed to do what I expected (erase the code because false is not true; keeping the code because true is true)