Thread overview | |||||
---|---|---|---|---|---|
|
July 09, 2014 __VERSION__ and the different compilers | ||||
---|---|---|---|---|
| ||||
Is it safe to assume that __VERSION__ is the same among DMD, LDC and GDC when using the equivalent front-end? I want to implement @nogc in Derelict in a backward compatible way. The simple thing to do is (at the suggestion of w0rp): static if( __VERSION__ < 2.066 ) enum nogc = 1; I just want to verify that this is sufficient and that I don't need to test for version(DMD) and friends as well. --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com |
July 09, 2014 Re: __VERSION__ and the different compilers | ||||
---|---|---|---|---|
| ||||
Posted in reply to Mike Parker | Mike Parker:
> Is it safe to assume that __VERSION__ is the same among DMD, LDC and GDC when using the equivalent front-end?
Right. An alternative solution is to use __traits(compiles) and use @nogc inside it.
Bye,
bearophile
|
July 09, 2014 Re: __VERSION__ and the different compilers | ||||
---|---|---|---|---|
| ||||
Posted in reply to Mike Parker | On 7/9/14, Mike Parker via Digitalmars-d-learn <digitalmars-d-learn@puremagic.com> wrote: > Is it safe to assume that __VERSION__ is the same among DMD, LDC and GDC when using the equivalent front-end? Yes, but not all future compilers might implement this (although I hope they will). I think there's also __VENDOR__ IIRC. |
Copyright © 1999-2021 by the D Language Foundation