Re: [Oorexx-devel] Question ad new .Message methods reply/replyWith

2022-05-19 Thread Rick McGuire
Those are not equivalent. The target message object is updated with the
supplied arguments and the copy is made after the update. The
original message object has a copy of the arguments used for the
invocation.

Rick

On Thu, May 19, 2022 at 4:21 AM Rony G. Flatscher 
wrote:

> While going through the send/With and start/With methods I "stumbled" over
> reply/With which I was not aware of that they got added.
>
> If understanding correctly, then reply/With is the same as start/With just
> creating a copy of the target message object to dispatch. If so, the same
> effect can be simply achieved in plain ooRexx code like:
>
> dispatchedMsg=msg~copy~start/With(...)
>
> If that is the case why would it be important to have new reply/With
> methods added for the .message class?
>
> ---rony
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel


[Oorexx-devel] Question ad new .Message methods reply/replyWith

2022-05-19 Thread Rony G. Flatscher
While going through the send/With and start/With methods I "stumbled" over reply/With which I was 
not aware of that they got added.


If understanding correctly, then reply/With is the same as start/With just creating a copy of the 
target message object to dispatch. If so, the same effect can be simply achieved in plain ooRexx 
code like:


   dispatchedMsg=msg~copy~start/With(...)

If that is the case why would it be important to have new reply/With methods added for the .message 
class?


---rony

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel