> > why you would wish to forgo the built-in cascading message feature > Nobody will have to give up using " ~~ ". Cascading message terms will stay as they are - everything unchanged.
it would not be necessary in ooRexx at all > Strictly speaking, it isn't necessary for any method to return the receiving object, but it's common practice for methods doing in-place modifications. E. g. in the Array class all four sort methods return self. In the MutableBuffer class append, (caseless)changeStr, delete, delStr, delWord, insert, lower, overlay, replaceAt, setBufferSize, setText, space, translate, and upper return self. Even []= returns self. On Mon, Nov 2, 2015 at 6:34 PM, Rony G. Flatscher <[email protected]> wrote: > Hi Erich, > > On 01.11.2015 18:07, Erich Steinböck wrote: > > I'd like to suggest to change (OrderedCollection's) appendAll and > (MapCollection's, Bag's and Set's) putAll methods to return the target > collection as their result. Currently they do not return a result. > > Any reasons not to do so, e.g. architectural concern, compatibility? > > Same suggestion for Array's fill method. > > All existing ~~appendAll/putAll/fill code should of course continue to > run unmodified, just the double "~" wouldn't be *required* any more. > > Hmm, the double-tilde ("cascading message" operator) is a great ooRexx > built-in feature that already does what you seek as you noted. It allows > ooRexx to cascade messages to any object, no matter whether it returns > itself or not. Other languages (e.g. like Java) do not have such a > mechanism and there it becomes mandatory to code methods such, that they > return the object for which the method runs. > > Therefore I am a little bit curious as to why you would wish to forgo the > built-in cascading message feature (the double-tildes) of ooRexx for > changing the methods to return the receiving object directly, as it would > not be necessary in ooRexx at all. > > ---rony > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > >
------------------------------------------------------------------------------
_______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
