rexxref documents the new MutableBuffer method = with three args, including the pad, in the brackets.
The supposedly equivalent replaceAt() method does have the pad as its last argument. But = doesn't actually accept the third pad argument and the source code has a comment "this is just replaceAt with the default pad". Do we treat this as a doc bug? Do we want = to be without pad?
_______________________________________________ Oorexx-devel mailing list Oorexxemail@example.com https://lists.sourceforge.net/lists/listinfo/oorexx-devel