"Nick Treleaven"  wrote in message news:lfsb5c$1kvi$1...@digitalmars.com...

Some discussion here:
https://d.puremagic.com/issues/show_bug.cgi?id=7417

I understand the argument about not allowing version(X && Y), but I do think this construct is ugly:

version(Foo) {} else { //code

Defining a version identifier NotFoo as well as Foo would be a bad solution.

What's wrong with:

version(!Foo) {}

This is one of the few areas where D is idealistic instead of pragmatic. For some reason Walter has decided unlike most things, this needs to be forced upon everyone.

This reminds me of banning goto and multiple returns because 'structured programming' prevents goto spaghetti madness. As always, it simply forces the programmer to jump through more hoops to get what they want.

Reply via email to