subject:"\[Issue 3167\] Passing result of a function call as ref argument no longer works"

[Issue 3167] Passing result of a function call as ref argument no longer works

2014-04-18 Thread via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=3167 Walter Bright changed: What|Removed |Added Version|1.046 |D1 --

[Issue 3167] Passing result of a function call as ref argument no longer works

2010-02-07 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=3167 --- Comment #16 from Don 2010-02-07 07:21:15 PST --- (In reply to comment #15) > (In reply to comment #13) > > It is invalid code because you are taking a reference to the return value > > of a > > function. Functions return, by definition, rv

[Issue 3167] Passing result of a function call as ref argument no longer works

2010-02-07 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=3167 --- Comment #15 from Eldar Insafutdinov 2010-02-07 03:05:52 PST --- (In reply to comment #13) > It is invalid code because you are taking a reference to the return value of a > function. Functions return, by definition, rvalues. You cannot tak

[Issue 3167] Passing result of a function call as ref argument no longer works

2010-01-29 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=3167 Steven Schveighoffer changed: What|Removed |Added CC||schvei...@yahoo.com --- Comment

[Issue 3167] Passing result of a function call as ref argument no longer works

2010-01-29 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=3167 --- Comment #13 from Walter Bright 2010-01-29 15:50:10 PST --- It is invalid code because you are taking a reference to the return value of a function. Functions return, by definition, rvalues. You cannot take a reference to an rvalue. -- Co

[Issue 3167] Passing result of a function call as ref argument no longer works

2010-01-29 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=3167 Eldar Insafutdinov changed: What|Removed |Added CC||e.insafutdi...@gmail.com --- Comm

[Issue 3167] Passing result of a function call as ref argument no longer works

2010-01-29 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=3167 Andrei Alexandrescu changed: What|Removed |Added CC||and...@metalanguage.com --- Comm

[Issue 3167] Passing result of a function call as ref argument no longer works

2010-01-29 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=3167 Walter Bright changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[Issue 3167] Passing result of a function call as ref argument no longer works

2009-10-15 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=3167 Don changed: What|Removed |Added CC||2kor...@gmail.com --- Comment #9 from Don 2009-

[Issue 3167] Passing result of a function call as ref argument no longer works

2009-08-15 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=3167 --- Comment #8 from Bill Baxter 2009-08-15 03:38:43 PDT --- (In reply to comment #7) > What if X is replaced by int? Should that work? I think it's a problem. Well, probably not, because 'int' is not a large struct. So the only reason to p

[Issue 3167] Passing result of a function call as ref argument no longer works

2009-08-14 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=3167 Walter Bright changed: What|Removed |Added CC||bugzi...@digitalmars.com --- Comment

[Issue 3167] Passing result of a function call as ref argument no longer works

2009-08-06 Thread d-bugmail

http://d.puremagic.com/issues/show_bug.cgi?id=3167 --- Comment #6 from Don 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 behavi