Re: [Oorexx-devel] Problem with "DO...OVER" ...

2016-11-11 Thread Gil Barmwater
Finally have a chance to add my thoughts on this. When I read the reference on DO OVER, I would not expect an UNKNOWN method to satisfy the required condition so, to me, this is not a bug. However, I can see the that the opposite view might have some merit. I would suggest opening an RFE inst

Re: [Oorexx-devel] Problem with "DO...OVER" ...

2016-11-07 Thread Rony G. Flatscher
On 06.11.2016 17:35, Erich Steinböck wrote: > rexxref says that for DO OVER Collection, a MAKEARRAY method is required, but > that's not the full > story: Rexx uses the REQUEST("ARRAY") mechanism to do the conversion, which > will send a MAKEARRAY > message, and if no such method exists, will fa

Re: [Oorexx-devel] Problem with "DO...OVER" ...

2016-11-06 Thread Erich Steinböck
rexxref says that for DO OVER Collection, a MAKEARRAY method is required, but that's not the full story: Rexx uses the REQUEST("ARRAY") mechanism to do the conversion, which will send a MAKEARRAY message, and if no such method exists, will fail (as documented) without testing for an UNKNOWN method.

Re: [Oorexx-devel] Problem with "DO...OVER" ...

2016-11-06 Thread Rony G. Flatscher
Another observation. After BSF4ooRexx gets based on Java 1.6/6.0 I have started to work on extending DO...OVER for java.lang.Iterable, java.util.Enumeration, java.util.Collection, java.util.Iterator and java.util.Map to make it transparent for Rexx programmers what kind of a Java collection is