[Issue 7854] Non-C attributes allowed on extern(C) function parameters

2012-04-12 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7854 --- Comment #6 from Jonathan M Davis 2012-04-12 23:07:41 PDT --- < I'm not exactly talking about binding or calling convention, I'm more talking < about types. To me, the two are orthogonal. Whereas I would argue that since you're declaring

[Issue 7895] New: Internal compiler error

2012-04-12 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7895 Summary: Internal compiler error Product: D Version: D2 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: DMD Assi

[Issue 7894] New: [CTFE] - goto within ForStatement restarts loop

2012-04-12 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7894 Summary: [CTFE] - goto within ForStatement restarts loop Product: D Version: D2 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Com

[Issue 7854] Non-C attributes allowed on extern(C) function parameters

2012-04-12 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7854 --- Comment #5 from Steven Schveighoffer 2012-04-12 14:28:18 PDT --- (In reply to comment #3) > (In reply to comment #2) > > extern(C) does not have any effect on parameters. > > Not so. It most definitely does! Doesn't make much difference

[Issue 7854] Non-C attributes allowed on extern(C) function parameters

2012-04-12 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7854 --- Comment #4 from Steven Schveighoffer 2012-04-12 14:20:09 PDT --- (In reply to comment #3) > > I agree it is probably a spec issue. Spec issues are normally treated with DMD > + spec keyword. It is part of the DMD download. >From descript

[Issue 7854] Non-C attributes allowed on extern(C) function parameters

2012-04-12 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7854 Don changed: What|Removed |Added Keywords||spec Component|websites

[Issue 7854] Non-C attributes allowed on extern(C) function parameters

2012-04-12 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7854 Steven Schveighoffer changed: What|Removed |Added CC||schvei...@yahoo.com Com

[Issue 6544] Tuple unpacking at the called function

2012-04-12 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=6544 --- Comment #3 from bearophile_h...@eml.cc 2012-04-12 10:05:16 PDT --- See also: http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&article_id=163993 Or: http://forum.dlang.org/thread/wwohddndnzdcdkwjo...@forum.dlang.org

[Issue 7891] int[] broken in vararg if it appears after 5 arguments of type bool

2012-04-12 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7891 Don changed: What|Removed |Added CC||clugd...@yahoo.com.au --- Comment #1 from Don 2

[Issue 7893] Spec completely wrong for D variadic arguments on 64 bits

2012-04-12 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7893 --- Comment #1 from Don 2012-04-12 07:33:14 PDT --- And also the second example in the spec (involving core.vararg) doesn't compile, because it refers to a non-existent print() function: _arguments[i].print(); -- Configure issuemail: http://

[Issue 7893] New: Spec completely wrong for D variadic arguments on 64 bits

2012-04-12 Thread d-bugmail
http://d.puremagic.com/issues/show_bug.cgi?id=7893 Summary: Spec completely wrong for D variadic arguments on 64 bits Product: D Version: D1 & D2 Platform: All OS/Version: All Status: NEW Severity: blocker