Re: [Oorexx-devel] At revision r11833

2019-03-11 Thread Rick McGuire
No, new is not a thing defined by the Rexx I/O standard. There is some error checking done there, but NOTREADY and a default return value is defined for the I/O operations. Rick On Mon, Mar 11, 2019 at 8:14 AM Enrico Sorichetti via Oorexx-devel < oorexx-devel@lists.sourceforge.net> wrote: >

Re: [Oorexx-devel] At revision r11833

2019-03-11 Thread Enrico Sorichetti via Oorexx-devel
Then it should raise one also on f = copies("F",444) o=.stream~new(f) Enrico PS ooRexx competitor… regina Issues the proper error message [enrico@enrico-imac tests]$/opt/Regina/bin/rexx d.regina 3 +++ call lineout f , "a truckload of waste" Error 40 running

Re: [Oorexx-devel] At revision r11833

2019-03-11 Thread Rick McGuire
Because it is not allowed to. Rexx streams raise a NOTREADY condition for any failures. Rick On Mon, Mar 11, 2019 at 6:53 AM Enrico Sorichetti via Oorexx-devel < oorexx-devel@lists.sourceforge.net> wrote: > It works ! > Thank You > Enrico > > PS > Now it is time to find out why rexx does not

Re: [Oorexx-devel] At revision r11833

2019-03-11 Thread Enrico Sorichetti via Oorexx-devel
It works ! Thank You Enrico PS Now it is time to find out why rexx does not complain about d = copies("D",6000) call sysmkdir(d) f = copies("F",6000) call lineout f , "a truckload of waste" o=.stream~new(f) o~open("replace" ) o~lineout("a truckload of waste" ) o~close Same behaviour since

Re: [Oorexx-devel] At revision r11833

2019-03-11 Thread Rick McGuire
Ok, I found it...I am really, really surprised this never happened when I was running the tests or Rony had never seen this when he was playing around with the classes. Rick On Mon, Mar 11, 2019 at 6:21 AM Enrico Sorichetti via Oorexx-devel < oorexx-devel@lists.sourceforge.net> wrote: > No

Re: [Oorexx-devel] At revision r11833

2019-03-11 Thread Enrico Sorichetti via Oorexx-devel
No tests were running All happened after the display of the final report E > On 11 Mar 2019, at 10:56, Rick McGuire wrote: > > Do you know what test was being run? An exception at that point doesn't > really make sense. > > Rick > ___

Re: [Oorexx-devel] At revision r11833

2019-03-11 Thread Erich Steinböck
> > what test was being run? > The exception happens (on all Jenkins build slaves we have) after all tests are finished and the final stats have been printed. ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net

Re: [Oorexx-devel] At revision r11833

2019-03-11 Thread Rick McGuire
Do you know what test was being run? An exception at that point doesn't really make sense. Rick On Mon, Mar 11, 2019 at 4:55 AM Enrico Sorichetti via Oorexx-devel < oorexx-devel@lists.sourceforge.net> wrote: > Running the testSuite > > 10 times on 10 runs > > > Process 7363 stopped > * thread

[Oorexx-devel] At revision r11833

2019-03-11 Thread Enrico Sorichetti via Oorexx-devel
Running the testSuite 10 times on 10 runs Process 7363 stopped * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x1b8) frame #0: 0x000100170a69 librexx.5.0.0.dylib`Activity::cleanupMutexes(this=0x00010200ef10) at Activity.cpp:3505