On 11/11/16 8:21 AM, Nick Sabalausky wrote:
On 11/11/2016 04:54 AM, Kagamin wrote:
On Thursday, 10 November 2016 at 13:58:56 UTC, Steven Schveighoffer
wrote:
Only possibility is just to ignore ALL cycles, and print them if any
are detected.

Run the new detector and if it fails, run the old one, if it succeeds,
print a message.

Or:

Run the new dmd. If it fails, either fix your code or go temporarily go
back to the old dmd until you can fix your code.


The option to ignore the cycles is there, added to allow for people to use the new DMD even if cycles exist. However, it is a runtime switch, which means you have to run it that way.

-Steve

              • ... Nick Sabalausky via Digitalmars-d-announce
              • ... Dicebot via Digitalmars-d-announce
              • ... Steven Schveighoffer via Digitalmars-d-announce
              • ... Dicebot via Digitalmars-d-announce
              • ... Steven Schveighoffer via Digitalmars-d-announce
              • ... Nick Sabalausky via Digitalmars-d-announce
              • ... jmh530 via Digitalmars-d-announce
              • ... Steven Schveighoffer via Digitalmars-d-announce
              • ... Jonathan M Davis via Digitalmars-d-announce
              • ... Dicebot via Digitalmars-d-announce
              • ... Steven Schveighoffer via Digitalmars-d-announce
              • ... Rainer Schuetze via Digitalmars-d-announce
              • ... Steven Schveighoffer via Digitalmars-d-announce
        • Re: Release D... Steven Schveighoffer via Digitalmars-d-announce
  • Re: Release D 2.072.0 Jack Stouffer via Digitalmars-d-announce
  • Re: Release D 2.072.0 Andre Pany via Digitalmars-d-announce

Reply via email to