http://d.puremagic.com/issues/show_bug.cgi?id=2464
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|minor |enhancement
--- Comment #1 fr
http://d.puremagic.com/issues/show_bug.cgi?id=2464
--- Comment #2 from [EMAIL PROTECTED] 2008-11-20 18:22 ---
This isn't a matter of compiler internals being messed up -- this is consistent
and, I believe, deliberate behavior. Unusual, but useful once you're used to
it.
Inserting a d
http://d.puremagic.com/issues/show_bug.cgi?id=2464
--- Comment #3 from [EMAIL PROTECTED] 2008-11-20 18:30 ---
Currently DMD gives an error type in this cases, which is just an alias to int.
It would be nice if it were a type that acted as an int, or anything else, but
didn't produce s
http://d.puremagic.com/issues/show_bug.cgi?id=2464
--- Comment #4 from [EMAIL PROTECTED] 2008-11-20 20:04 ---
re: #2 and #3: Good points, but this issue seems different to me. I understand
why the compiler reports extra errors on code that uses a previously undefined
variable:
char[]
http://d.puremagic.com/issues/show_bug.cgi?id=2464
--- Comment #5 from [EMAIL PROTECTED] 2008-11-20 20:37 ---
Ah, right. I see that in FuncExp::semantic there's:
---
if (global.errors)
{
if (!fd->type->next)
fd->type->next = Type::terror;
}
---
Which basically says "If t
http://d.puremagic.com/issues/show_bug.cgi?id=2464
Don changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
