Re: #ifdef hell

2015-11-02 Thread Joakim via Digitalmars-d
On Thursday, 29 October 2015 at 23:55:14 UTC, Jonathan M Davis wrote: The idea is that you get rid of all of the & and ||ing that tends to make #ifdefs really hard to follow and error-prone. And by having each version fully separate, changing one version won't break another. Now, that comes

Re: #ifdef hell

2015-11-02 Thread Daniel Murphy via Digitalmars-d
On 31/10/2015 12:01 AM, Jacob Carlborg wrote: On 2015-10-30 03:01, Walter Bright wrote: I might add that over time, I'd been removing #if's and #ifdef's from the dmd front end source code. The results were very satisfactory - the code was easier to read, understand and maintain. It also made

Re: #ifdef hell

2015-10-30 Thread Jacob Carlborg via Digitalmars-d
On 2015-10-30 03:01, Walter Bright wrote: I might add that over time, I'd been removing #if's and #ifdef's from the dmd front end source code. The results were very satisfactory - the code was easier to read, understand and maintain. It also made running magicport on the code practical. The

Re: #ifdef hell

2015-10-30 Thread anonymous via Digitalmars-d
On Thursday, 29 October 2015 at 23:10:38 UTC, Walter Bright wrote: On 10/29/2015 3:23 PM, rsw0x wrote: On Thursday, 29 October 2015 at 22:18:11 UTC, Walter Bright wrote: https://www.cqse.eu/en/blog/living-in-the-ifdef-hell/ Another voice on what is wrong with the snarl of #ifdef's. how does

#ifdef hell

2015-10-29 Thread Walter Bright via Digitalmars-d
https://www.cqse.eu/en/blog/living-in-the-ifdef-hell/ Another voice on what is wrong with the snarl of #ifdef's.

Re: #ifdef hell

2015-10-29 Thread Walter Bright via Digitalmars-d
On 10/29/2015 3:18 PM, Walter Bright wrote: https://www.cqse.eu/en/blog/living-in-the-ifdef-hell/ Another voice on what is wrong with the snarl of #ifdef's. Reddit: https://www.reddit.com/r/programming/comments/3qo79b/living_in_the_ifdef_hell/

Re: #ifdef hell

2015-10-29 Thread rsw0x via Digitalmars-d
On Thursday, 29 October 2015 at 22:18:11 UTC, Walter Bright wrote: https://www.cqse.eu/en/blog/living-in-the-ifdef-hell/ Another voice on what is wrong with the snarl of #ifdef's. how does this differ from static if and version(x) hell?

Re: #ifdef hell

2015-10-29 Thread Walter Bright via Digitalmars-d
On 10/29/2015 3:23 PM, rsw0x wrote: On Thursday, 29 October 2015 at 22:18:11 UTC, Walter Bright wrote: https://www.cqse.eu/en/blog/living-in-the-ifdef-hell/ Another voice on what is wrong with the snarl of #ifdef's. how does this differ from static if and version(x) hell? We advise people

Re: #ifdef hell

2015-10-29 Thread David Nadlinger via Digitalmars-d
On Thursday, 29 October 2015 at 23:10:38 UTC, Walter Bright wrote: On 10/29/2015 3:23 PM, rsw0x wrote: On Thursday, 29 October 2015 at 22:18:11 UTC, Walter Bright wrote: https://www.cqse.eu/en/blog/living-in-the-ifdef-hell/ Another voice on what is wrong with the snarl of #ifdef's. how does

Re: #ifdef hell

2015-10-29 Thread Jonathan M Davis via Digitalmars-d
On Thursday, 29 October 2015 at 23:14:26 UTC, David Nadlinger wrote: On Thursday, 29 October 2015 at 23:10:38 UTC, Walter Bright wrote: We advise people not to use static if to do what version(x) eschews, and suggest better alternatives. Ha, I wish! In fact, you are currently arguing for

Re: #ifdef hell

2015-10-29 Thread Walter Bright via Digitalmars-d
On 10/29/2015 4:14 PM, David Nadlinger wrote: In fact, you are currently arguing for people to write *more* version statements over at the https://github.com/D-Programming-Language/dmd/pull/5231 I presented several ways to avoid using complex version statements. I might add that over time,