Rick McGuire <[email protected]> wrote: > These are fundamentally different constructs. Do Over actually requests a > new version from the collection which is defined as being non-sparse. The > sort is an in-place modification of the array itself.
REXX used to have a principle of least astonishment. You're saying that to be un-astonished a user has to know the inner workings of the implementation which seems, well, astonishing. [snip] > Raising an error if a~items < a~size would mean the above scenario would > only work if there were exactly 1000 items added to the array. The > dichotomy between items and size and the meaning of sparse is intentional. > This change is not going to be made. Is it possible then that a decent explanation that ordinary users can understand can be put into the relevant doc? -- Jeremy Nicoll - my opinions are my own ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
