Re: Release D 2.072.0

2016-11-11 Thread Jonathan M Davis via Digitalmars-d-announce
On Friday, November 11, 2016 14:36:59 Nick Sabalausky via Digitalmars-d- announce wrote: > On 11/11/2016 08:30 AM, Dicebot wrote: > > On Friday, 11 November 2016 at 13:21:40 UTC, Nick Sabalausky wrote: > >> Run the new dmd. If it fails, either fix your code or go temporarily > >> go back to the

Re: Article: Running D without its runtime

2016-11-11 Thread Guillaume Piolat via Digitalmars-d-announce
On Thursday, 10 November 2016 at 06:52:12 UTC, Olivier Pisano wrote: I cannot read your website on Firefox 45 (no text is displayed). It works on chromium anyway. FWIW it should work now

Re: Release D 2.072.0

2016-11-11 Thread Steven Schveighoffer via Digitalmars-d-announce
On 11/11/16 3:02 PM, jmh530 wrote: On Friday, 11 November 2016 at 19:36:59 UTC, Nick Sabalausky wrote: I've gone through a lot of compiler upgrades on a lot of D projects, and in my experience, this "investigate and fix for the new dmd" has always been trivial (aside from one instance where

Re: JavaScript ( QScript Qt-5 ) in GUI framework QtE5

2016-11-11 Thread MGW via Digitalmars-d-announce
Warm-up for mind. Visual Basic 6 is used as framework for DLL on D. Calls of functions from VB to D and from D to VB are available that allows to control the form on VB directly from DLL on D. https://pp.vk.me/c638421/v638421885/9bee/0KJYM0QafWQ.jpg

Re: Release D 2.072.0

2016-11-11 Thread jmh530 via Digitalmars-d-announce
On Friday, 11 November 2016 at 19:36:59 UTC, Nick Sabalausky wrote: I've gone through a lot of compiler upgrades on a lot of D projects, and in my experience, this "investigate and fix for the new dmd" has always been trivial (aside from one instance where Phobos's standard function

Re: Release D 2.072.0

2016-11-11 Thread Nick Sabalausky via Digitalmars-d-announce
On 11/11/2016 08:30 AM, Dicebot wrote: On Friday, 11 November 2016 at 13:21:40 UTC, Nick Sabalausky wrote: 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. D will never be considered production ready as pong as this

Re: Release D 2.072.0

2016-11-11 Thread Steven Schveighoffer via Digitalmars-d-announce
On 11/11/16 9:02 AM, Dicebot wrote: On 11/11/2016 03:46 PM, Steven Schveighoffer wrote: ... or one can spend one extra hour to implement deprecation path and the issue disappears completely. There is a misunderstanding that the new cycle detection is an "upgrade" of some kind. It's a bug fix.

Re: Release D 2.072.0

2016-11-11 Thread Steven Schveighoffer via Digitalmars-d-announce
On 11/11/16 9:06 AM, Rainer Schuetze wrote: On 11.11.2016 14:42, Steven Schveighoffer wrote: 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. You can also

Re: Release D 2.072.0

2016-11-11 Thread Rainer Schuetze via Digitalmars-d-announce
On 11.11.2016 14:42, Steven Schveighoffer wrote: 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.

Re: Release D 2.072.0

2016-11-11 Thread Dicebot via Digitalmars-d-announce
On 11/11/2016 03:46 PM, Steven Schveighoffer wrote: >> ... or one can spend one extra hour to implement deprecation path and >> the issue disappears completely. > > There is a misunderstanding that the new cycle detection is an "upgrade" > of some kind. It's a bug fix. There is no difference

Re: Release D 2.072.0

2016-11-11 Thread Steven Schveighoffer via Digitalmars-d-announce
On 11/11/16 8:30 AM, Dicebot wrote: On Friday, 11 November 2016 at 13:21:40 UTC, Nick Sabalausky wrote: 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. D will never be considered production ready as pong as this attiude

Re: Release D 2.072.0

2016-11-11 Thread Steven Schveighoffer via Digitalmars-d-announce
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

Re: Release D 2.072.0

2016-11-11 Thread Dicebot via Digitalmars-d-announce
On Friday, 11 November 2016 at 13:21:40 UTC, Nick Sabalausky wrote: 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. D will never be considered production ready as pong as this attiude remaind. Your described scenario in

Re: Release D 2.072.0

2016-11-11 Thread Nick Sabalausky via Digitalmars-d-announce
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:

Re: Release D 2.072.0

2016-11-11 Thread Kagamin via Digitalmars-d-announce
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.