three times to the routine object in the loop, causing the
routine "worker" to run
on three different threads, where in each thread the executed routine then
waits on the event
semaphore ("wait" message to the event semaphore). The main program then sleeps
for five seconds,
before
POINT ONE
The logic to determine the MAXIMUM_FILENAME_LENGTH is broken
the relevant code form the rexx sources
#include
#include
#if defined(PATH_MAX)
# define MAXIMUM_PATH_LENGTH PATH_MAX + 1
#elif defined(_POSIX_PATH_MAX)
# define MAXIMUM_PATH_LENGTH _POSIX_PATH_MAX + 1
#else
# define MAX
Here is the patch to
fix the MAXIMUM_FILENAME_LENGTH glitch
Implement .RexxInfo~getMaxFileNameLength
[enrico@enrico-imac tests]$rexx -e "say .rexxinfo~maxfilenamelength"
255
[enrico@enrico-imac tests]$rexx -e "say .rexxinfo~maxpathlength"
1024
[enrico@enrico-imac tests]$
Index: interpreter/clas
Would really work better as a class method of the .File class rather than
on RexxInfo. That's where we tend to put file system related stuff.
Rick
On Thu, Mar 7, 2019 at 5:22 PM Enrico Sorichetti via Oorexx-devel <
oorexx-devel@lists.sourceforge.net> wrote:
> Here is the patch to
> fix the MAXIM
You are the expert on that!
I just cloned the logic already implemented for maxpathlength
Enrico
PS.
For my education I will try to implement both of them as methods of the .File
class
In my sandbox
> On 7 Mar 2019, at 23:27, Rick McGuire wrote:
>
> Would really work better as a class met
n event semaphore and sends the message "reset"
> to it. Then it sends the "start" message three times to the routine object
> in the loop, causing the routine "worker" to run on three different
> threads, where in each thread the executed routine then waits on
