Re: [Oorexx-devel] rexxc.testGroup fails and logo/test counts repeat

d to compile with rc 0"    >O> "" => "'EMPTY 0' Rexx code expected to compile with rc 0"    >A> "'EMPTY 0' Rexx code expected to compile with rc 0"    102 *-*   self~assertTrue(s.0 > 0, "rexxc" self~t

Re: [Oorexx-devel] rexxc.testGroup fails and logo/test counts repeat

TY 0" > >O> "" => "'EMPTY 0" > >L> "' Rexx code expected to compile with rc 0" > >O> "" => "'EMPTY 0' Rexx code expected to compile with rc 0" >

Re: [Oorexx-devel] rexxc.testGroup fails and logo/test counts repeat

t;    >A> "'EMPTY 0' Rexx code expected to compile with rc 0"    101 *-*   self~assertTrue(s.0 > 0, "rexxc" self~testSource "is expected to produce a few lines of output")    >V> SELF => "a rexxc.testGroup"    >C> 

Re: [Oorexx-devel] unix/rexxutil event and mutex functions are really broken.

On Fri, Dec 7, 2018 at 8:56 AM Enrico Sorichetti via Oorexx-devel < oorexx-devel@lists.sourceforge.net> wrote: > > > On 7 Dec 2018, at 14:30, Rick McGuire wrote: > > That's a memory management library and doesn't appear to have anything to > do with cross-process semaphores. > > > But it has for

Re: [Oorexx-devel] unix/rexxutil event and mutex functions are really broken.

Acording to this post sem_init does not exist on macOS so it cannot work: https://stackoverflow.com/questions/6230734/posix-semaphores-synchronization-problem Read the EDIT below the code snippet. Can’t prov

Re: [Oorexx-devel] unix/rexxutil event and mutex functions are really broken.

> On 7 Dec 2018, at 14:30, Rick McGuire wrote: > > That's a memory management library and doesn't appear to have anything to do > with cross-process semaphores. But it has for threads … My mistake was not to look at the other sources involved to discover that semaphores support was only f

Re: [Oorexx-devel] unix/rexxutil event and mutex functions are really broken.

That's a memory management library and doesn't appear to have anything to do with cross-process semaphores. Rick On Fri, Dec 7, 2018 at 8:26 AM Enrico Sorichetti via Oorexx-devel < oorexx-devel@lists.sourceforge.net> wrote: > You might get some ideas by looking at how the Boehm GC does it > Enri

Re: [Oorexx-devel] unix/rexxutil event and mutex functions are really broken.

You might get some ideas by looking at how the Boehm GC does it Enrico > On 7 Dec 2018, at 14:15, Rick McGuire wrote: > > Ignoring for a moment the elephant in the corner of the Apple deprecated (and > non-functional) sem_* functions, the *ix versions of the semaphore functions > are really s

[Oorexx-devel] unix/rexxutil event and mutex functions are really broken.

Ignoring for a moment the elephant in the corner of the Apple deprecated (and non-functional) sem_* functions, the *ix versions of the semaphore functions are really sort of broken. For the event semaphores, one of the functions is a reset, which uses sem_init() to perform the reset. This probably

Re: [Oorexx-devel] rexxc.testGroup fails and logo/test counts repeat

Dec 2018 > OS Name:SUNOS > SysVersion: SunOS illumos-3e90f8d31d.5.11 > > Tests ran: 22435 > Assertions: 375322 > Failures: 3 > Errors: 0 > > [failure] [20181207 04:04:00.128320] >svn:r11562 Ch

Re: [Oorexx-devel] New 5.0.0 Beta Build for Windows

It is possible, but generally the Windows is implied by the .exe extension. Rick On Fri, Dec 7, 2018 at 4:53 AM Jon Wolfers wrote: > Is it possible and sensible for the Windows installers to have 'Windows' > in their name ie: >ooRexx.5.0.0.11579-Windowsx86_32.exe >

Re: [Oorexx-devel] New 5.0.0 Beta Build for Windows

Is it possible and sensible for the Windows installers to have 'Windows' in their name ie: ooRexx.5.0.0.11579-Windowsx86_32.exe ? Jon On Thu, 6 Dec 2018 at 22:53, Erich Steinböck wrote: >

[Oorexx-devel] rexxc.testGroup fails and logo/test counts repeat

-3e90f8d31d.5.11 Tests ran:  22435 Assertions: 375322 Failures:   3 Errors: 0 [failure] [20181207 04:04:00.128320]   svn:    r11562   Change date: 2018-12-03 23:45:29 +0100   Test:   TEST_REXXC_ONE_ARG   Class:  rexxc.testGroup   File: /export/home/agrellum