[Issue 3196] Segfault(mtype.c) almost any error involving a delegate inside a function
http://d.puremagic.com/issues/show_bug.cgi?id=3196 --- Comment #3 from Don clugd...@yahoo.com.au 2009-08-06 00:00:57 PDT --- *** Issue 3227 has been marked as a duplicate of this issue. *** -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 3228] Segfault(mtype.c) multiple empty delegates
http://d.puremagic.com/issues/show_bug.cgi?id=3228 Don clugd...@yahoo.com.au changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Comment #1 from Don clugd...@yahoo.com.au 2009-08-06 00:01:17 PDT --- *** This issue has been marked as a duplicate of issue 3196 *** -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 3196] Segfault(mtype.c) almost any error involving a delegate inside a function
http://d.puremagic.com/issues/show_bug.cgi?id=3196 --- Comment #4 from Don clugd...@yahoo.com.au 2009-08-06 00:01:17 PDT --- *** Issue 3228 has been marked as a duplicate of this issue. *** -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 3167] Passing result of a function call as ref argument no longer works
http://d.puremagic.com/issues/show_bug.cgi?id=3167 Don clugd...@yahoo.com.au changed: What|Removed |Added CC||clugd...@yahoo.com.au --- Comment #4 from Don clugd...@yahoo.com.au 2009-08-06 00:08:01 PDT --- (In reply to comment #3) I'm fairly sure this was by design (bug 2621) in D 2.026, but I don't think it was expected to seep through to D1. It might be related to the fix for bug #2323 ? My patch for that bug was rejected, so I don't know what changes were made. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 3167] Passing result of a function call as ref argument no longer works
http://d.puremagic.com/issues/show_bug.cgi?id=3167 Bill Baxter wbax...@gmail.com changed: What|Removed |Added CC||wbax...@gmail.com --- Comment #5 from Bill Baxter wbax...@gmail.com 2009-08-06 06:40:55 PDT --- (In reply to comment #3) I'm fairly sure this was by design (bug 2621) in D 2.026, but I don't think it was expected to seep through to D1. I hope you're right. In D2 you can have the ref argument be const (which I hope eliminates the error), but in D1 you have no such option. So you often have to resort to making arguments 'ref' for efficiency even when the function doesn't modify the argument. Also the error message could be a little clearer. Something like Can't pass a temporary to a function taking a ref argument would be a lot clearer I think. Passing something to a function taking a ref does not necessarily imply assigning to that ref argument in D1, for the reason stated above. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 3167] Passing result of a function call as ref argument no longer works
http://d.puremagic.com/issues/show_bug.cgi?id=3167 --- Comment #6 from Don clugd...@yahoo.com.au 2009-08-06 12:24:14 PDT --- This change is clearly caused by the addition of the new function Expression *CallExp::modifiableLvalue(Scope *sc, Expression *e) in expression.c. Comment it out to restore the old behaviour. It doesn't seem to be necessary for any bug fixes -- eg, removing it doesn't reactivate bug 2323. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 1311] DMD 1.018: Fix for bug657 breaks other code
http://d.puremagic.com/issues/show_bug.cgi?id=1311 Don clugd...@yahoo.com.au changed: What|Removed |Added Status|NEW |RESOLVED CC||clugd...@yahoo.com.au Resolution||FIXED --- Comment #3 from Don clugd...@yahoo.com.au 2009-08-06 13:13:18 PDT --- The functionality was restored by introducing extern(System) for exactly this situation. I'll mark this as fixed. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 3231] Function declared to return a type with its same name doesn't compile
http://d.puremagic.com/issues/show_bug.cgi?id=3231 --- Comment #1 from Tim M tim.matthe...@gmail.com 2009-08-06 16:37:53 PDT --- The error reported: test.d(11): Error: function test.Foo.Bar is used as a type -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 3231] Function declared to return a type with its same name doesn't compile
http://d.puremagic.com/issues/show_bug.cgi?id=3231
BCS shro8...@vandals.uidaho.edu changed:
What|Removed |Added
CC||shro8...@vandals.uidaho.edu
--- Comment #4 from BCS shro8...@vandals.uidaho.edu 2009-08-06 17:53:44 PDT
---
I also think this is invalid.
As a work around:
class Bar
{
}
class Foo
{
.Bar Bar() // note '.' to start from global scope
{
return null;
}
}
void main()
{
}
--
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
[Issue 3231] Function declared to return a type with its same name doesn't compile
http://d.puremagic.com/issues/show_bug.cgi?id=3231 --- Comment #6 from Jarrett Billingsley jarrett.billings...@gmail.com 2009-08-06 22:22:05 PDT --- (In reply to comment #5) The bug was filed as a blocker for the .net implementation because there are cases like this System.Text.RegularExpressions that has a static Match Match(System.String, System.String) method. I think that marking the bug as invalid because of a limitation in the implementation is ridiculous. It's not a limitation in the implementation, it's how the language is defined. Java - and by proxy, C#, since MS doesn't seem to have strayed too far from their inspiration - allows for multiple symbols of the same name to be distinguished based on how they're used. D does not. If you have a disagreement, it's with the spec, not the implementation. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
