Steven Schveighoffer wrote in message
news:op.xbs1naiueav7ka@stevens-macbook-pro.local...
A wild wild guess is that there was code in the compiler that used to
require it (after all, it was required a long time ago), and somehow it
got reactivated by accident.
But wild guesses don't help
Daniel Murphy:
D language has similar rules, but I don't rember if the D
compiler warns against usage of similar identifiers.
It doesn't!
Perhaps it should?
[snip etc]
The D compiler is not a lint tool!
Currently the D compiler catches several bugs that are caught
only by C lints.
Andrei Alexandrescu:
http://www.reddit.com/r/programming/comments/1yts5n/facebook_open_sources_flint_a_c_linter_written_in/
An interesting comment from Reddit:
klusarkI've been trying to build this for the past hour. It
requires folly. folly requires some double-conversion library,
but you
bearophile wrote in message news:bskrlqgtwkqdyoqwk...@forum.dlang.org...
D language has similar rules, but I don't rember if the D
compiler warns against usage of similar identifiers.
It doesn't!
[snip etc]
The D compiler is not a lint tool!
Dicebot:
It should be other way around - remove all such arguable
warnings from compiler to dedicated lint tool and never add any
single one to compiler.
What are the advantages and disadvantages of doing as you say?
Bye,
bearophile
On Tuesday, 25 February 2014 at 11:20:37 UTC, bearophile wrote:
Currently the D compiler catches several bugs that are caught
only by C lints. Clang shows that you can add lot of lint-like
tests to the compiler. I'd like some more tests in the D
compiler.
Full stop. It should be other way
On Tuesday, 25 February 2014 at 12:58:03 UTC, bearophile wrote:
Dicebot:
It should be other way around - remove all such arguable
warnings from compiler to dedicated lint tool and never add
any single one to compiler.
What are the advantages and disadvantages of doing as you say?
Bye,
On Tuesday, 25 February 2014 at 11:22:23 UTC, bearophile wrote:
Andrei Alexandrescu:
http://www.reddit.com/r/programming/comments/1yts5n/facebook_open_sources_flint_a_c_linter_written_in/
An interesting comment from Reddit:
klusarkI've been trying to build this for the past hour. It
On Tuesday, 25 February 2014 at 10:28:41 UTC, Daniel Murphy wrote:
Walter + Andrei did it, and it was completely intentional, and
it was known that it would break code.
https://github.com/D-Programming-Language/dmd/pull/3054
I find it so ironical that Walter warns that this may break the
I'd like to point out a cool fact: with D, we can do a number of
lint like things in the language itself, especially if we extend
rtinfo (I wrote about this a little while ago and might do a pull
request soon)
checkBlacklistedIdentifiers -- would require modifying the header
but we could
Dicebot wrote in message news:rkgevwccvxaynrbbi...@forum.dlang.org...
Full stop. It should be other way around - remove all such
arguable warnings from compiler to dedicated lint tool and never
add any single one to compiler.
Exactly.
This sort of thing would make an excellent compiler
Am 25.02.2014 13:48, schrieb Dicebot:
On Tuesday, 25 February 2014 at 11:20:37 UTC, bearophile wrote:
Currently the D compiler catches several bugs that are caught only by
C lints. Clang shows that you can add lot of lint-like tests to the
compiler. I'd like some more tests in the D compiler.
You don't need to port lints to use them.
Paulo Pinto:
End result being a portable macro assembler, as safe as,
writing in pure assembly.
I'd even like warnings active on default in D, plus a compiler
switch to disable them. Lot of people in D.learn don't even
activate warnings.
Bye,
bearophile
On Tuesday, 25 February 2014 at 15:43:30 UTC, bearophile wrote:
I'd even like warnings active on default in D, plus a compiler
switch to disable them. Lot of people in D.learn don't even
activate warnings.
Those warning that _can_ be activated by default, should be just
turned into errors.
Am 25.02.2014 16:49, schrieb Dicebot:
On Tuesday, 25 February 2014 at 15:43:30 UTC, bearophile wrote:
I'd even like warnings active on default in D, plus a compiler switch
to disable them. Lot of people in D.learn don't even activate warnings.
Those warning that _can_ be activated by default,
Dicebot:
Those warning that _can_ be activated by default, should be
just turned into errors. Same crap as with C.
Programming is not a black/white thing
(http://en.wiktionary.org/wiki/Manichaean#Adjective ) :-)
Bye,
bearophile
On Tuesday, 25 February 2014 at 16:07:34 UTC, bearophile wrote:
Programming is not a black/white thing
(http://en.wiktionary.org/wiki/Manichaean#Adjective ) :-)
Which is exactly why you can't put this stuff into compiler -
providing comparable amount of cofigurability as expected from
On Tue, 25 Feb 2014 05:28:42 -0500, Daniel Murphy
yebbliesnos...@gmail.com wrote:
Steven Schveighoffer wrote in message
news:op.xbs1naiueav7ka@stevens-macbook-pro.local...
A wild wild guess is that there was code in the compiler that used to
require it (after all, it was required a long
On 2014-02-24 21:29, Walter Bright wrote:
Looks like we need to do something about this:
http://www.reddit.com/r/programming/comments/1ytfc5/d_2065_released_with_396_fixes_and_improvements/cfnmkih
At a minimum, add it to the changelog. Or possibly remove that change.
I've been compiling
On Monday, 24 February 2014 at 08:45:31 UTC, Andrew Edwards wrote:
The final release of DMD 2.065 is now available. [1] contains
complete descriptions of all changes, enhancements and fixes
for this release.
Nice job wrangling the new release schedule and shepherding your
first release out the
On 2014-02-24 21:29, Walter Bright wrote:
Looks like we need to do something about this:
http://www.reddit.com/r/programming/comments/1ytfc5/d_2065_released_with_396_fixes_and_improvements/cfnmkih
At a minimum, add it to the changelog. Or possibly remove that change.
Answering some of your
On Tuesday, 25 February 2014 at 12:58:03 UTC, bearophile wrote:
Dicebot:
It should be other way around - remove all such arguable
warnings from compiler to dedicated lint tool and never add
any single one to compiler.
What are the advantages and disadvantages of doing as you say?
On Tue, 25 Feb 2014 12:11:46 -0500, Steven Schveighoffer
schvei...@yahoo.com wrote:
I would suggest a proper interim fix is to only reject key types that
define opEquals, but not opCmp. Then switch to using equals in druntime.
Sorry, I meant define opCmp but not opEquals. Some types can be
On 2/25/14, 3:07 PM, deadalnix wrote:
On Tuesday, 25 February 2014 at 12:58:03 UTC, bearophile wrote:
Dicebot:
It should be other way around - remove all such arguable warnings
from compiler to dedicated lint tool and never add any single one to
compiler.
What are the advantages and
On Monday, 24 February 2014 at 20:24:04 UTC, Walter Bright wrote:
On 2/24/2014 9:48 AM, Brad Anderson wrote:
On Monday, 24 February 2014 at 17:42:07 UTC, Manu wrote:
First thing I noticed though, the Windows installer seemed to
forget where
my existing D installation is, and tried to install
On Tuesday, 25 February 2014 at 18:34:49 UTC, Ary Borenszweig
wrote:
Yes, it can be a separate module in the source code of the
compiler.
The compiler is the only one that has most information to
provide lint errors.
If the lint has tests, if you change the compiler you
immediately can
On 2/25/2014 2:28 AM, Daniel Murphy wrote:
Walter + Andrei did it, and it was completely intentional, and it was known that
it would break code.
https://github.com/D-Programming-Language/dmd/pull/3054
It was intended to only break code that was already broken (would fail at
runtime). It
On 2/25/2014 11:03 AM, Brad Anderson wrote:
On Monday, 24 February 2014 at 20:24:04 UTC, Walter Bright wrote:
On 2/24/2014 9:48 AM, Brad Anderson wrote:
On Monday, 24 February 2014 at 17:42:07 UTC, Manu wrote:
First thing I noticed though, the Windows installer seemed to forget where
my
On 2/25/2014 6:53 AM, Adam D. Ruppe wrote:
well a lot of these are obviated by D itself too... but checking reflection,
especially with a project-wide rtinfo extension so you don't have to static
assert in every module, gives D the potential to lint itself with some
user-defined semantics.
On 25 February 2014 17:30, Jacob Carlborg d...@me.com wrote:
On 2014-02-24 21:29, Walter Bright wrote:
Looks like we need to do something about this:
http://www.reddit.com/r/programming/comments/1ytfc5/d_2065_released_with_396_fixes_and_improvements/cfnmkih
At a minimum, add it to the
On 2/25/2014 10:34 AM, Ary Borenszweig wrote:
If it's separated then it's always the turtle chasing the rabbit.
I like Adam's idea of improving reflection so such linters could be written as D
code and compiled in.
On 2/24/2014 12:29 PM, Walter Bright wrote:
Looks like we need to do something about this:
http://www.reddit.com/r/programming/comments/1ytfc5/d_2065_released_with_396_fixes_and_improvements/cfnmkih
At a minimum, add it to the changelog. Or possibly remove that change.
24-Feb-2014 12:45, Andrew Edwards пишет:
The final release of DMD 2.065 is now available. [1] contains complete
descriptions of all changes, enhancements and fixes for this release.
Available binaries can be accessed at [2]. Since the website will lag
slightly behind, links are provided below
On Tue, 25 Feb 2014 14:33:05 -0500, Walter Bright
newshou...@digitalmars.com wrote:
On 2/25/2014 2:28 AM, Daniel Murphy wrote:
Walter + Andrei did it, and it was completely intentional, and it was
known that
it would break code.
https://github.com/D-Programming-Language/dmd/pull/3054
It
On 2014-02-25 20:49, Steven Schveighoffer wrote:
I just wrote this and compiled on 2.064:
import std.stdio;
struct S
{
int x;
int y;
bool opEquals(ref const(S) other) const { return other.x == x;}
}
void main()
{
int[S] aa;
aa[S(1, 2)] = 5;
aa[S(1, 3)] = 6;
Am 25.02.2014 20:36, schrieb Walter Bright:
On 2/25/2014 10:34 AM, Ary Borenszweig wrote:
If it's separated then it's always the turtle chasing the rabbit.
I like Adam's idea of improving reflection so such linters could be
written as D code and compiled in.
Yes, other languages are
On Tue, 25 Feb 2014 15:12:41 -0500, Jacob Carlborg d...@me.com wrote:
The thing is that the compiler complains about a deceleration looking
like this:
struct TagIndex
{
uint tag, index;
}
If the compiler generates opEquals and opCmp, then it's guaranteed
opEquals(x, y) is
On 2/25/2014 12:54 PM, Paulo Pinto wrote:
Am 25.02.2014 20:36, schrieb Walter Bright:
On 2/25/2014 10:34 AM, Ary Borenszweig wrote:
If it's separated then it's always the turtle chasing the rabbit.
I like Adam's idea of improving reflection so such linters could be
written as D code and
On 2/25/2014 7:36 AM, Paulo Pinto wrote:
Yeah, it worked really great for C.
Developers created C compilers in other systems and never ported lint
as part of the process.
End result being a portable macro assembler, as safe as, writing in pure
assembly.
This is hyperbole. C's type system
On 2/25/2014 8:05 AM, Paulo Pinto wrote:
Actually a good approach the Go guys have, everything that can be a warning, is
an error.
D started with and maintained that approach for many years. It was a position I
strongly advocated.
On Tuesday, 25 February 2014 at 22:42:53 UTC, Walter Bright wrote:
On 2/25/2014 8:05 AM, Paulo Pinto wrote:
Actually a good approach the Go guys have, everything that can
be a warning, is
an error.
D started with and maintained that approach for many years. It
was a position I strongly
On 2/25/2014 2:47 PM, Dicebot wrote:
To be completely honest,
I should hope so :-)
at the moment warning lobby has happened it was more
reasonable because there was not even slight possibility of lint-like tool
creation back then. But now we have DScanner and DDMD is not that far away too
On 2/25/14, 3:22 AM, bearophile wrote:
Andrei Alexandrescu:
http://www.reddit.com/r/programming/comments/1yts5n/facebook_open_sources_flint_a_c_linter_written_in/
An interesting comment from Reddit:
klusarkI've been trying to build this for the past hour. It requires
folly. folly requires
On 2/24/14, 4:46 PM, bachmeier wrote:
On Monday, 24 February 2014 at 21:07:00 UTC, Andrei Alexandrescu wrote:
This is a first on so many levels.
https://news.ycombinator.com/item?id=7293396
http://www.reddit.com/r/programming/comments/1yts5n/facebook_open_sources_flint_a_c_linter_written_in/
Andrei Alexandrescu:
Ironically that's for the obsoleted C++ program. The D program
is trivial to build.
Oh, I didn't know/understand that. Sorry for the noise.
Bye,
bearophile
On 2/25/2014 3:40 PM, Andrei Alexandrescu wrote:
Ironically that's for the obsoleted C++ program. The D program is trivial to
build.
Maybe the C++ version should undergo a git rm :-)
Or at least, put it on another branch.
On Tuesday, 25 February 2014 at 23:40:02 UTC, Andrei Alexandrescu
wrote:
On 2/25/14, 3:22 AM, bearophile wrote:
Andrei Alexandrescu:
http://www.reddit.com/r/programming/comments/1yts5n/facebook_open_sources_flint_a_c_linter_written_in/
An interesting comment from Reddit:
klusarkI've been
On Monday, 24 February 2014 at 16:30:43 UTC, Steve Teale wrote:
On Monday, 17 February 2014 at 17:56:08 UTC, Steve Teale wrote:
On Monday, 17 February 2014 at 06:57:55 UTC, Steve Teale wrote:
I would love to get some feedback on both the application and
the documentation
You must forgive me
On Tuesday, 25 February 2014 at 00:46:03 UTC, bachmeier wrote:
On Monday, 24 February 2014 at 21:07:00 UTC, Andrei
Alexandrescu wrote:
This is a first on so many levels.
https://news.ycombinator.com/item?id=7293396
On Friday, 21 February 2014 at 20:34:12 UTC, Walter Bright wrote:
dlang.org and dconf.org now support https,
https://dlang.org
https://dconf.org
Note that this is a self-signed certificate, and so when you
first access it you'll get a dire warning from your browser.
Captcha in the forum to
On Tuesday, 25 February 2014 at 19:37:04 UTC, Walter Bright wrote:
This is a most interesting idea. Please pursue.
I talked about it a little while ago in a thread on the forum
(it was also my dconf submission but since I don't really want to
travel anyway that surely won't happen).
On Tuesday, 25 February 2014 at 23:40:02 UTC, Andrei Alexandrescu
wrote:
On 2/25/14, 3:22 AM, bearophile wrote:
Andrei Alexandrescu:
http://www.reddit.com/r/programming/comments/1yts5n/facebook_open_sources_flint_a_c_linter_written_in/
An interesting comment from Reddit:
klusarkI've been
On Wednesday, 26 February 2014 at 00:57:55 UTC, deadalnix wrote:
Usually, I understand XXX evangelist as My job is to use
twitter.
Oh, so _that's_ why the text of the Bible comes in individual
numbered verses of less than 140 characters each!
On Wednesday, 26 February 2014 at 01:47:24 UTC, Andrei
Alexandrescu wrote:
I like throwErrno and friends a lot.
What's that? git grep over folly's repo comes up with 0 results.
Is this like our cenforce? (I think it should be made public.)
On Tuesday, 25 February 2014 at 22:37:46 UTC, Walter Bright wrote:
On 2/25/2014 7:36 AM, Paulo Pinto wrote:
Yeah, it worked really great for C.
Developers created C compilers in other systems and never
ported lint
as part of the process.
End result being a portable macro assembler, as safe
56 matches
Mail list logo
