David Nadlinger wrote in message
news:tsxbhkdfwilqjpqek...@forum.dlang.org...
Second, if I'm using -w, I'm typically interested in errors if I write
fishy code, not because some third-party library I just updated made a
small change to its API. I don't see where the advantage would be in
On 4 Oct 2014 22:30, David Nadlinger via Digitalmars-d
digitalmars-d@puremagic.com wrote:
On Monday, 29 September 2014 at 15:13:28 UTC, Daniel Murphy wrote:
But that's a good thing - the people who get their code broken are the
people who are asking for it with '-w'.
I don't think there is
On 5 Oct 2014 08:10, Daniel Murphy via Digitalmars-d
digitalmars-d@puremagic.com wrote:
David Nadlinger wrote in message
news:tsxbhkdfwilqjpqek...@forum.dlang.org...
Second, if I'm using -w, I'm typically interested in errors if I write
fishy code, not because some third-party library I
On Friday, September 26, 2014 23:12:47 Daniel Kozák via Digitalmars-d wrote:
The only one and right solution is print warning message by default
- Původní zpráva -
Od:David Nadlinger via Digitalmars-d digitalmars-d@puremagic.com
Odesláno:26. 9. 2014 18:20
On Monday, 29 September 2014 at 15:13:28 UTC, Daniel Murphy wrote:
But that's a good thing - the people who get their code broken
are the people who are asking for it with '-w'.
I don't think there is much merit to this argument.
First, it's not like the ability to make diagnostics halt the
2014-09-27 1:15 GMT+09:00 David Nadlinger via Digitalmars-d
digitalmars-d@puremagic.com:
As Walter mentioned in a recent pull request discussion [1], the first
formal deprecation protocol we came up with for language changes looked
something like this:
1. remove from documentation
2.
On Friday, 26 September 2014 at 16:31:52 UTC, H. S. Teoh via
Digitalmars-d wrote:
I think the warning stage is still necessary. Users need to be
informed
well ahead of time that something is going to be deprecated,
before it
starts breaking their builds (which, according to recommended
usage,
On Friday, 26 September 2014 at 21:13:14 UTC, Daniel Kozák via
Digitalmars-d wrote:
The only one and right solution is print warning message by
default
This is actually what is done for deprecations already. -dw is
the default. We just currently don't use them this way, for
whatever reasons.
On Friday, 26 September 2014 at 18:38:43 UTC, Steven
Schveighoffer wrote:
Case against:
https://github.com/D-Programming-Language/phobos/pull/2254#issuecomment-52764718
I don't think this is relevant for this discussion at all.
Vladimir asked for advance notice in terms of docs before
On Monday, 29 September 2014 at 10:15:07 UTC, David Nadlinger
wrote:
On Friday, 26 September 2014 at 18:38:43 UTC, Steven
Schveighoffer wrote:
Case against:
https://github.com/D-Programming-Language/phobos/pull/2254#issuecomment-52764718
I don't think this is relevant for this discussion at
David Nadlinger wrote in message
news:hqjjujxwydtzpgfcn...@forum.dlang.org...
As far as I can see having deprecation messages as Warnings first actually
leads to *more* build breakage (as many more people are building with -w
than with -de) and less time for adapting code before it is made
On 09/29/2014 11:58 AM, David Nadlinger wrote:
As far as I can see having deprecation messages as Warnings first
actually leads to *more* build breakage (as many more people are
building with -w than with -de) and less time for adapting code before
it is made an error (because -w/-wi is not the
As Walter mentioned in a recent pull request discussion [1], the
first formal deprecation protocol we came up with for language
changes looked something like this:
1. remove from documentation
2. warning
3. deprecation
4. error
(The remove from documentation step is a bit questionable, but
On Fri, Sep 26, 2014 at 04:15:40PM +, David Nadlinger via Digitalmars-d
wrote:
As Walter mentioned in a recent pull request discussion [1], the first
formal deprecation protocol we came up with for language changes
looked something like this:
1. remove from documentation
2. warning
3.
On 9/26/14 12:15 PM, David Nadlinger wrote:
As Walter mentioned in a recent pull request discussion [1], the first
formal deprecation protocol we came up with for language changes looked
something like this:
1. remove from documentation
2. warning
3. deprecation
4. error
(The remove from
The only one and right solution is print warning message by default
- Původní zpráva -
Od:David Nadlinger via Digitalmars-d digitalmars-d@puremagic.com
Odesláno:26. 9. 2014 18:20
Komu:digitalmars-d@puremagic.com digitalmars-d@puremagic.com
Předmět:Deprecations: Any reason left for
Daniel Kozák:
The only one and right solution is print warning message by
default
I am asking for this since some years.
Bye,
bearophile
On Fri, Sep 26, 2014 at 09:16:50PM +, bearophile via Digitalmars-d wrote:
Daniel Kozák:
The only one and right solution is print warning message by default
I am asking for this since some years.
[...]
In git HEAD, dmd now allows use of deprecated features and displays a
warning by
H. S. Teoh:
In git HEAD, dmd now allows use of deprecated features and
displays a warning by default.
I meant I'd like by default all warnings to be shown :-)
Bye,
bearophile
19 matches
Mail list logo
