The old behavior was a bug. Because the array class had a makestring method, it should have been used for things like say and other uses where a string value was required. I won't go into the reasons why, but this was never properly implemented. I fixed this in (I believe) the 4.0 release, but backed the fix out when I discovered the implementation had a problem that could crash the interpreter. This problem was fixed in 5.0 and the correct behavior was restored.
Rick On Tue, Aug 16, 2016 at 8:02 PM, Gil Barmwater <[email protected]> wrote: > I was just playing with the new ooRexx5.0.0 Beta and noticed a change in > behavior. In earlier releases, the code > > trio = .array~of(1,2,3); say trio > > produced "an Array". However, in 5.0.0, it produces 3 lines containing > 1, 2 and 3 respectively, the same as > > say trio~makeString. > > Reading the documentation it appears the new behavior is the correct one > and the old one was a bug but I didn't find a bug for it in the Changes > document. So the questions are 1) was this intentional (fixing an > incorrect result) and if so, where is it documented, and 2) will this > change cause old programs to break (quite possibly) and is the risk > acceptable? > > -- > Gil Barmwater > > > ------------------------------------------------------------ > ------------------ > _______________________________________________ > 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
