Well, this also happens with String. The first argument is consumed and never gets received by INIT. If you want to do something with the string, you have to write your version of NEW. I found that while writing TUTOR.
Josep Maria Missatge de Rony G. Flatscher <[email protected]> del dia dl., 3 de nov. 2025 a les 14:49: > rexxref.pdf states the following in "4.2.9. Initialization": > > 4.2.9. Initialization > > Any object requiring initialization at creation time must define an INIT > method. If this method is defined, the class object runs the INIT method > after the object is created. If an object has more than one INIT method > (for example, it is defined in several classes), each INIT method must > forward the INIT message up the hierarchy to complete the object's > initialization. > > The Object's NEW class method (and some other classes) adhere to this > protocol, but others like Array's NEW class method does not. > > The question is, how to asses this? Is this an error in the implementation > of e.g. the Array NEW class method, that it does not send an INIT message > to the newly created array object? And if it is an error, should all > arguments given to the NEW message be forwarded to the INIT method, or > should those argument that the NEW method uses be regarded to be consumed > and not forwarded to the newly created object? In the latter case this > would have to be documented as well. > > So, what is the take on this? > > ---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
