Re: [Oorexx-devel] High memory usage in ooRexx

2017-06-29 Thread Chip Davis
Not in any way to assert that ooRexx does not have scaling issues, when I hear hoof-beats I think "horses" not "reindeer". ;-) I would want to be very sure that the long execution times and random anomalies were not caused by my code before asking volunteers to debug it. -Chip- On 6/29/2017

Re: [Oorexx-devel] High memory usage in ooRexx

2017-06-29 Thread Rony G. Flatscher
Erich: On 29.06.2017 17:11, Erich Steinböck wrote: > > executing other peoples code .. please give it a try > > I can run code if you provide it as a platform-independent test case. I have > no Mac, and the Mac > binaries you provide won't run on Ubuntu or Windows, the platforms I can test

Re: [Oorexx-devel] High memory usage in ooRexx

2017-06-29 Thread Erich Steinböck
Hi P.O., executing other peoples code .. please give it a try I can run code if you provide it as a platform-independent test case. I have no Mac, and the Mac binaries you provide won't run on Ubuntu or Windows, the platforms I can test on. tr.rex gets stuck in the routine split_data > The code

Re: [Oorexx-devel] ooRexx FTP

2017-06-29 Thread Erich Steinböck
Bill, don't use ftpTrace if you don't want trace output to be displayed. Use ftpTraceLog / ftpTraceLogOff to write trace output to a file. Instead of creating and (if required) reading a trace log file, you might consider the command trace data available through the CmdResponse method. Here's an e