Re: [eigen] Refactoring around ReturnByValue

[ Thread Index | Date Index | More Archives ]


basically, after the evaluator refactoring, ReturnByValue won't be
needed, at least for Eigen stuff because all functions (inverse,
solve, etc.) will return pure semantic expression.

Nevertheless, we can still keep the current ReturnByValue for backward
compatibility and convenience.


2011/4/11 Adolfo Rodríguez Tsouroukdissian <adolfo.rodriguez@xxxxxxxxxxxxxxxx>:
> Hi list,
> On the workplan for the expression evaluator that will ship with 3.1 [1],
> there is a task named "Finish the refactoring around ReturnByValue". I
> recently learned about the ReturnByValue expression type thanks to Benoit,
> and I've begun to us it quite a bit in a pet project I'm working on (very
> happy with it). Now, my question would be, how will this refactoring affect
> code written with 3.0's ReturnByValue type. Will the way to write these
> expressions change, and if so how?.
> TIA,
> Adolfo.
> [1]
> --
> Adolfo Rodríguez Tsouroukdissian
> Robotics engineer
> Tel. +34.93.414.53.47
> Fax.+
> CONFIDENTIALITY NOTICE: This e-mail and the accompanying document(s) may
> contain confidential information which is privileged and intended only for
> the individual or entity to whom they are addressed.  If you are not the
> intended recipient, you are hereby notified that any disclosure, copying,
> distribution or use of this e-mail and/or accompanying document(s) is
> strictly prohibited.  If you have received this e-mail in error, please
> immediately notify the sender at the above e-mail address.

Mail converted by MHonArc 2.6.19+