Re: [Oorexx-devel] Releasing ooRexx 5.0? Building on Debian Linux Shared Web Hosting as non-root

[Michael Lueck]

Greetings Team,


Michael Lueck wrote:

On to make install finally... maybe during lunch (shortly).


(uiserver):u40009095:~/build/oorexxbuild/release$ make install
[  3%] Built target class_files
[ 10%] Built target rexxapi
[ 82%] Built target rexx
[ 83%] Built target hostemu
[ 83%] Built target rexx_exe
[ 88%] Built target rxapi
[ 89%] Built target rexxutil
[ 89%] Built target rexximage
[ 90%] Built target rexx_img
[ 91%] Generating rexx.1.gz
[ 91%] Built target rexx_man
[ 91%] Built target rexxc
[ 92%] Generating rexxc.1.gz
[ 92%] Built target rexxc_man
[ 93%] Built target rxmath
[ 93%] Built target rxqueue
[ 93%] Generating rxqueue.1.gz
[ 93%] Built target rxqueue_man
[ 94%] Built target rxregexp
[ 95%] Built target rxsock
[ 95%] Built target rxsubcom
[ 96%] Generating rxsubcom.1.gz
[ 96%] Built target rxsubcom_man
[ 96%] Built target rxunixsys
[ 96%] Built target runRexxProgram
[ 96%] Built target stackOverflow
[ 96%] Built target callrexx1
[ 96%] Built target callrexx2
[ 97%] Built target wpipe1
[ 97%] Built target wpipe2
[ 98%] Built target wpipe3
[ 98%] Built target orxclassic
[ 98%] Built target orxclassic1
[ 99%] Built target orxexits
[ 99%] Built target orxfunction
[100%] Built target orxinvocation
[100%] Built target orxmethod
[100%] Built target rexxinstance
Install the project...
-- Install configuration: "RELEASE"
-- Installing: 
/homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxapi.so.5.0.0
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxapi.so
-- Set runtime path of 
"/homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxapi.so.5.0.0" to 
"$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxapi.so.3
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxapi.so.4
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexx.so.5.0.0
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexx.so
-- Set runtime path of "/homepages/35/d157794216/htdocs/opt/oorexx/lib/librexx.so.5.0.0" 
to "$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexx.so.3
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexx.so.4
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/bin/rexx
-- Set runtime path of "/homepages/35/d157794216/htdocs/opt/oorexx/bin/rexx" to 
"$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/rexx.img
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/bin/rxapi
-- Set runtime path of "/homepages/35/d157794216/htdocs/opt/oorexx/bin/rxapi" to 
"$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/bin/rexxc
-- Set runtime path of "/homepages/35/d157794216/htdocs/opt/oorexx/bin/rexxc" to 
"$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/bin/rxqueue
-- Set runtime path of "/homepages/35/d157794216/htdocs/opt/oorexx/bin/rxqueue" to 
"$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/bin/rxsubcom
-- Set runtime path of "/homepages/35/d157794216/htdocs/opt/oorexx/bin/rxsubcom" to 
"$ORIGIN/../lib"
-- Installing: 
/homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxutil.so.5.0.0
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxutil.so
-- Set runtime path of 
"/homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxutil.so.5.0.0" to 
"$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxutil.so.3
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librexxutil.so.4
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxmath.so.5.0.0
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxmath.so
-- Set runtime path of 
"/homepages/35/d157794216/htdocs/opt/oorexx/lib/librxmath.so.5.0.0" to 
"$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxmath.so.3
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxmath.so.4
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxsock.so.5.0.0
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxsock.so
-- Set runtime path of 
"/homepages/35/d157794216/htdocs/opt/oorexx/lib/librxsock.so.5.0.0" to 
"$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxsock.so.3
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxsock.so.4
-- Installing: 
/homepages/35/d157794216/htdocs/opt/oorexx/lib/librxregexp.so.5.0.0
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxregexp.so
-- Set runtime path of 
"/homepages/35/d157794216/htdocs/opt/oorexx/lib/librxregexp.so.5.0.0" to 
"$ORIGIN/../lib"
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxregexp.so.3
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/librxregexp.so.4
-- Installing: 
/homepages/35/d157794216/htdocs/opt/oorexx/lib/libhostemu.so.5.0.0
-- Installing: /homepages/35/d157794216/htdocs/opt/oorexx/lib/libhostemu.so
-- Set runtime path

[Oorexx-devel] Building on Windows

[P.O. Jonsson]

Dear Erich,

I wanted to download the latest build for Windows and could only find a version 
11671 from 19.1.2019, quite some time ago.

I looked at the Jenkins slave and it reports a successful build today or 
yesterday ooRexx-5.0.0-11724.windows.x86_64.exe, but this file is not to be 
seen at the sourceforge download site.

Can you please have a look? The building seems to go fine, just the upload 
seems to fail.

PS I am building my own Windows from source now to check the sample test cases, 
the first run on Mac works now.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se




___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Question on SysFileTree()

[P.O. Jonsson]

This works for my purpose. Tnx !

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se




> Am 07.02.2019 um 13:52 schrieb Michael Lueck :
> 
> Greetings ooRexx'ers,
> 
> Rick McGuire wrote:
>> The path in SysSearchPath() is the name of an environment variable, not a 
>> string containing the path. You could set an environment variable with that 
>> path and use SysSearchPath, but that's a bit silly since you are just 
>> checking for the existence of a single file in a specific location, not 
>> search. I'd use something like this:
>> f = .file~new('~/workspace/ooRexx-macOS1014-build/oorexxBuild/bin/rexx')
>> if f~exists then 
> 
> 
> In my class library, I have a method FullyQualifyFINDfilename that is meant 
> to work on both file system objects which do exists AND filespec's that do 
> not actually exist on disk.
> 
> I make use of the following core ooRexx to do the majority of cleanup:
> 
>   /* Use the Object Rexx stream object / qualify method to do as much work as 
> we can get it to do... */
> 
>   FINDstream = .stream~new(FINDfilenamequery)
> 
>   FINDfilename = FINDstream~qualify
> 
>   drop FINDstream
> 
> 
> 
> This does simplification of . .. and so on that may appear in the 
> FINDfilenamequery passed into the method.
> 
> I am thankful,
> 
> -- 
> Michael Lueck
> Lueck Data Systems
> http://www.lueckdatasystems.com/
> 
> 
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Question on SysFileTree()

[Michael Lueck]

Greetings ooRexx'ers,

Rick McGuire wrote:
The path in SysSearchPath() is the name of an environment variable, not a string containing the path. You could set an environment variable with that path and use SysSearchPath, but that's a bit silly 
since you are just checking for the existence of a single file in a specific location, not search. I'd use something like this:


f = .file~new('~/workspace/ooRexx-macOS1014-build/oorexxBuild/bin/rexx')
if f~exists then 



In my class library, I have a method FullyQualifyFINDfilename that is meant to 
work on both file system objects which do exists AND filespec's that do not 
actually exist on disk.

I make use of the following core ooRexx to do the majority of cleanup:

   /* Use the Object Rexx stream object / qualify method to do as much work as 
we can get it to do... */

   FINDstream = .stream~new(FINDfilenamequery)

   FINDfilename = FINDstream~qualify

   drop FINDstream



This does simplification of . .. and so on that may appear in the 
FINDfilenamequery passed into the method.

I am thankful,

--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/


___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Question on SysFileTree()

[Rony G. Flatscher]

On 07.02.2019 12:25, P.O. Jonsson wrote:
> Thanks for clarifying.
>
> Maybe you (or someone else) can help me with another issue: I am trying to 
> locate the build
> directory on Mac in FileUtils.cls. On the jenkins slave the build is located 
> in:
>
> //Users/jenkins/workspace/ooRexx-macOS1014-build/oorexxBuild/
>
> And in my clone installation:
>
> //Users/po/workspace/ooRexx-macOS1014-build/oorexxBuild/
>
> I was trying to locate it using SysSearchPath() but his does not work:
>
> /dir = SysSearchPath('~/workspace/ooRexx-macOS1014-build/oorexxBuild/bin', 
> "rexx")/
>
> Can you or someone else point me to a reliable way to locate the build 
> directory on Mac? I have
> tried the Unix alternatives in FileUtils.cls but they do not work.

If I understand your use case correctly, you would have a need to locate where 
"rexx[.exe]" (the
executable) that gets used is located?

If so, I do not know of a solution. If no one else has a reliable, 
multi-platform solution you could
open a RFE, e.g. that this path is supplied via the .rexxInfo class (cf. 
rexxref.pdf, 5.4.15) or the
like.

---rony


___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Question on SysFileTree()

[Rick McGuire]

The path in SysSearchPath() is the name of an environment variable, not a
string containing the path. You could set an environment variable with that
path and use SysSearchPath, but that's a bit silly since you are just
checking for the existence of a single file in a specific location, not
search. I'd use something like this:

f = .file~new('~/workspace/ooRexx-macOS1014-build/oorexxBuild/bin/rexx')
if f~exists then 

Rick

On Thu, Feb 7, 2019 at 6:25 AM P.O. Jonsson  wrote:

> Thanks for clarifying.
>
> Maybe you (or someone else) can help me with another issue: I am trying to
> locate the build directory on Mac in FileUtils.cls. On the jenkins slave
> the build is located in:
>
> */Users/jenkins/workspace/ooRexx-macOS1014-build/oorexxBuild*
>
> And in my clone installation:
>
> */Users/po/workspace/ooRexx-macOS1014-build/oorexxBuild*
>
> I was trying to locate it using SysSearchPath() but his does not work:
>
> *dir = SysSearchPath('~/workspace/ooRexx-macOS1014-build/oorexxBuild/bin',
> "rexx")*
>
> Can you or someone else point me to a reliable way to locate the build
> directory on Mac? I have tried the Unix alternatives in FileUtils.cls but
> they do not work.
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
>
>
>
>
> Am 07.02.2019 um 12:11 schrieb Rick McGuire :
>
> Yes, there are differences in how the platforms deal with it, depending on
> what the different systems provide for us. We have to deal with it as well.
> We're not going to recreate the file systems just to fix every little
> difference.
>
> Rick
>
> On Thu, Feb 7, 2019 at 6:07 AM P.O. Jonsson  wrote:
>
>> Ok for MAC then but on Windows this does not occur, two backslashes are
>> still present in f.1. in my example. So at least SysFileTree works
>> differently in this aspect.
>>
>> I can live with this, no problem, I just found it weird to have my input
>> „corrected“ rather than being told I did a mistake.
>>
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se
>>
>>
>>
>>
>> Am 07.02.2019 um 11:53 schrieb Rick McGuire :
>>
>> Before the search, the name gets canonicalized. Things like double
>> slashes and  ".", and ".." directories get fixed up to get the fully
>> resolved name before processing the search.
>>
>> Rick
>>
>> On Thu, Feb 7, 2019 at 5:36 AM P.O. Jonsson  wrote:
>>
>>> The fact that is „works“ is not a proof of it being valid. This is for
>>> me undefinded behaviour. In addition my point was that SysFileTree
>>> „corrected“ my input, i.e. removed double slashes from the path.
>>>
>>> Hälsningar/Regards/Grüsse,
>>> P.O. Jonsson
>>> oor...@jonases.se
>>>
>>>
>>>
>>>
>>> Am 07.02.2019 um 11:21 schrieb Enrico Sorichetti via Oorexx-devel <
>>> oorexx-devel@lists.sourceforge.net>:
>>>
>>> Dear P.O
>>>
>>> Having extra separators does not make a path invalid
>>>
>>> Just try with playing around with ls
>>>
>>> Just checked
>>>
>>> ls opt/ooRexx/bin///rexx
>>>
>>> ls opt/ooRexx/bin/
>>>
>>> E
>>>
>>>
>>>
>>>
>>> On 7 Feb 2019, at 11:09, P.O. Jonsson  wrote:
>>>
>>> Dear Developers,
>>>
>>> When working on modifying FileUtils.cls to work also for macOS/Darwin I
>>> used (by mistake, certainly) SysFileTree() with an invalid path and was
>>> astonished to see that it nevertheless produced a valid result. Is this
>>> intended?
>>>
>>> This is what I intended to do:
>>>
>>> *installDir = '/Users/po/Applications/ooRexx5.0.0‘*
>>> *name = 'rexx'*
>>> *j = SysFileTree(installDir'/bin/'name, f., 'FOS')*
>>>
>>> But instead I did (note the trailing slash)
>>>
>>> *installDir = '/Users/po/Applications/ooRexx5.0.0/‘*
>>> *name = 'rexx'*
>>> *j = SysFileTree(installDir'/bin/'name, f., 'FOS')*
>>>
>>> This produces a „//„ in the path, i.e. an illegal path
>>>
>>> Nevertheless SysFileTree() „corrected“ my input path, removed the
>>> additional slash and gave me the correct path back as f.1.
>>>
>>> I also tried on Windows and there SysFileTree() considers a path with
>>> double backslash to be correct (return value 0), but the output is not
>>> corrected as on MAC.
>>>
>>> I have attached two scripts to show the behavior , amend to fit your
>>> installation and have a try. I did not investigate on Linux/Unix.
>>>
>>> 
>>> 
>>>
>>> Hälsningar/Regards/Grüsse,
>>> P.O. Jonsson
>>> oor...@jonases.se
>>>
>>>
>>>
>>>
>>> ___
>>> Oorexx-devel mailing list
>>> Oorexx-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>>
>>>
>>> ___
>>> Oorexx-devel mailing list
>>> Oorexx-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>>
>>>
>>> ___
>>> Oorexx-devel mailing list
>>> Oorexx-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>>
>> ___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net
>> ht

Re: [Oorexx-devel] Question on SysFileTree()

[P.O. Jonsson]

Thanks for clarifying.

Maybe you (or someone else) can help me with another issue: I am trying to 
locate the build directory on Mac in FileUtils.cls. On the jenkins slave the 
build is located in:

/Users/jenkins/workspace/ooRexx-macOS1014-build/oorexxBuild

And in my clone installation:

/Users/po/workspace/ooRexx-macOS1014-build/oorexxBuild

I was trying to locate it using SysSearchPath() but his does not work:

dir = SysSearchPath('~/workspace/ooRexx-macOS1014-build/oorexxBuild/bin', 
"rexx")

Can you or someone else point me to a reliable way to locate the build 
directory on Mac? I have tried the Unix alternatives in FileUtils.cls but they 
do not work.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se




> Am 07.02.2019 um 12:11 schrieb Rick McGuire :
> 
> Yes, there are differences in how the platforms deal with it, depending on 
> what the different systems provide for us. We have to deal with it as well. 
> We're not going to recreate the file systems just to fix every little 
> difference. 
> 
> Rick
> 
> On Thu, Feb 7, 2019 at 6:07 AM P.O. Jonsson  > wrote:
> Ok for MAC then but on Windows this does not occur, two backslashes are still 
> present in f.1. in my example. So at least SysFileTree works differently in 
> this aspect.
> 
> I can live with this, no problem, I just found it weird to have my input 
> „corrected“ rather than being told I did a mistake.
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
> 
>> Am 07.02.2019 um 11:53 schrieb Rick McGuire > >:
>> 
>> Before the search, the name gets canonicalized. Things like double slashes 
>> and  ".", and ".." directories get fixed up to get the fully resolved name 
>> before processing the search. 
>> 
>> Rick
>> 
>> On Thu, Feb 7, 2019 at 5:36 AM P.O. Jonsson > > wrote:
>> The fact that is „works“ is not a proof of it being valid. This is for me 
>> undefinded behaviour. In addition my point was that SysFileTree „corrected“ 
>> my input, i.e. removed double slashes from the path.
>> 
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se 
>> 
>> 
>> 
>> 
>>> Am 07.02.2019 um 11:21 schrieb Enrico Sorichetti via Oorexx-devel 
>>> >> >:
>>> 
>>> Dear P.O
>>> 
>>> Having extra separators does not make a path invalid 
>>> 
>>> Just try with playing around with ls
>>> 
>>> Just checked 
>>> 
>>> ls opt/ooRexx/bin///rexx
>>> 
>>> ls opt/ooRexx/bin/
>>> 
>>> E
>>> 
>>> 
>>> 
>>> 
 On 7 Feb 2019, at 11:09, P.O. Jonsson >>> > wrote:
 
 Dear Developers,
 
 When working on modifying FileUtils.cls to work also for macOS/Darwin I 
 used (by mistake, certainly) SysFileTree() with an invalid path and was 
 astonished to see that it nevertheless produced a valid result. Is this 
 intended?
 
 This is what I intended to do:
 
 installDir = '/Users/po/Applications/ooRexx5.0.0‘
 name = 'rexx'
 j = SysFileTree(installDir'/bin/'name, f., 'FOS')
 
 But instead I did (note the trailing slash)
 
 installDir = '/Users/po/Applications/ooRexx5.0.0/‘
 name = 'rexx'
 j = SysFileTree(installDir'/bin/'name, f., 'FOS')
 
 This produces a „//„ in the path, i.e. an illegal path
 
 Nevertheless SysFileTree() „corrected“ my input path, removed the 
 additional slash and gave me the correct path back as f.1.
 
 I also tried on Windows and there SysFileTree() considers a path with 
 double backslash to be correct (return value 0), but the output is not 
 corrected as on MAC.
 
 I have attached two scripts to show the behavior , amend to fit your 
 installation and have a try. I did not investigate on Linux/Unix.
 
 
 
 
 Hälsningar/Regards/Grüsse,
 P.O. Jonsson
 oor...@jonases.se 
 
 
 
 
 ___
 Oorexx-devel mailing list
 Oorexx-devel@lists.sourceforge.net 
 
 https://lists.sourceforge.net/lists/listinfo/oorexx-devel 
 
>>> 
>>> ___
>>> Oorexx-devel mailing list
>>> Oorexx-devel@lists.sourceforge.net 
>>> 
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel 
>>> 
>> 
>> ___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net 
>> 
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel 
>> 
>> 

Re: [Oorexx-devel] Question on SysFileTree()

[Rick McGuire]

Yes, there are differences in how the platforms deal with it, depending on
what the different systems provide for us. We have to deal with it as well.
We're not going to recreate the file systems just to fix every little
difference.

Rick

On Thu, Feb 7, 2019 at 6:07 AM P.O. Jonsson  wrote:

> Ok for MAC then but on Windows this does not occur, two backslashes are
> still present in f.1. in my example. So at least SysFileTree works
> differently in this aspect.
>
> I can live with this, no problem, I just found it weird to have my input
> „corrected“ rather than being told I did a mistake.
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
>
>
>
>
> Am 07.02.2019 um 11:53 schrieb Rick McGuire :
>
> Before the search, the name gets canonicalized. Things like double slashes
> and  ".", and ".." directories get fixed up to get the fully resolved name
> before processing the search.
>
> Rick
>
> On Thu, Feb 7, 2019 at 5:36 AM P.O. Jonsson  wrote:
>
>> The fact that is „works“ is not a proof of it being valid. This is for me
>> undefinded behaviour. In addition my point was that SysFileTree „corrected“
>> my input, i.e. removed double slashes from the path.
>>
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se
>>
>>
>>
>>
>> Am 07.02.2019 um 11:21 schrieb Enrico Sorichetti via Oorexx-devel <
>> oorexx-devel@lists.sourceforge.net>:
>>
>> Dear P.O
>>
>> Having extra separators does not make a path invalid
>>
>> Just try with playing around with ls
>>
>> Just checked
>>
>> ls opt/ooRexx/bin///rexx
>>
>> ls opt/ooRexx/bin/
>>
>> E
>>
>>
>>
>>
>> On 7 Feb 2019, at 11:09, P.O. Jonsson  wrote:
>>
>> Dear Developers,
>>
>> When working on modifying FileUtils.cls to work also for macOS/Darwin I
>> used (by mistake, certainly) SysFileTree() with an invalid path and was
>> astonished to see that it nevertheless produced a valid result. Is this
>> intended?
>>
>> This is what I intended to do:
>>
>> *installDir = '/Users/po/Applications/ooRexx5.0.0‘*
>> *name = 'rexx'*
>> *j = SysFileTree(installDir'/bin/'name, f., 'FOS')*
>>
>> But instead I did (note the trailing slash)
>>
>> *installDir = '/Users/po/Applications/ooRexx5.0.0/‘*
>> *name = 'rexx'*
>> *j = SysFileTree(installDir'/bin/'name, f., 'FOS')*
>>
>> This produces a „//„ in the path, i.e. an illegal path
>>
>> Nevertheless SysFileTree() „corrected“ my input path, removed the
>> additional slash and gave me the correct path back as f.1.
>>
>> I also tried on Windows and there SysFileTree() considers a path with
>> double backslash to be correct (return value 0), but the output is not
>> corrected as on MAC.
>>
>> I have attached two scripts to show the behavior , amend to fit your
>> installation and have a try. I did not investigate on Linux/Unix.
>>
>> 
>> 
>>
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se
>>
>>
>>
>>
>> ___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
>>
>> ___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
>>
>> ___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Question on SysFileTree()

[P.O. Jonsson]

Ok for MAC then but on Windows this does not occur, two backslashes are still 
present in f.1. in my example. So at least SysFileTree works differently in 
this aspect.

I can live with this, no problem, I just found it weird to have my input 
„corrected“ rather than being told I did a mistake.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se




> Am 07.02.2019 um 11:53 schrieb Rick McGuire :
> 
> Before the search, the name gets canonicalized. Things like double slashes 
> and  ".", and ".." directories get fixed up to get the fully resolved name 
> before processing the search. 
> 
> Rick
> 
> On Thu, Feb 7, 2019 at 5:36 AM P.O. Jonsson  > wrote:
> The fact that is „works“ is not a proof of it being valid. This is for me 
> undefinded behaviour. In addition my point was that SysFileTree „corrected“ 
> my input, i.e. removed double slashes from the path.
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
> 
>> Am 07.02.2019 um 11:21 schrieb Enrico Sorichetti via Oorexx-devel 
>> > >:
>> 
>> Dear P.O
>> 
>> Having extra separators does not make a path invalid 
>> 
>> Just try with playing around with ls
>> 
>> Just checked 
>> 
>> ls opt/ooRexx/bin///rexx
>> 
>> ls opt/ooRexx/bin/
>> 
>> E
>> 
>> 
>> 
>> 
>>> On 7 Feb 2019, at 11:09, P.O. Jonsson >> > wrote:
>>> 
>>> Dear Developers,
>>> 
>>> When working on modifying FileUtils.cls to work also for macOS/Darwin I 
>>> used (by mistake, certainly) SysFileTree() with an invalid path and was 
>>> astonished to see that it nevertheless produced a valid result. Is this 
>>> intended?
>>> 
>>> This is what I intended to do:
>>> 
>>> installDir = '/Users/po/Applications/ooRexx5.0.0‘
>>> name = 'rexx'
>>> j = SysFileTree(installDir'/bin/'name, f., 'FOS')
>>> 
>>> But instead I did (note the trailing slash)
>>> 
>>> installDir = '/Users/po/Applications/ooRexx5.0.0/‘
>>> name = 'rexx'
>>> j = SysFileTree(installDir'/bin/'name, f., 'FOS')
>>> 
>>> This produces a „//„ in the path, i.e. an illegal path
>>> 
>>> Nevertheless SysFileTree() „corrected“ my input path, removed the 
>>> additional slash and gave me the correct path back as f.1.
>>> 
>>> I also tried on Windows and there SysFileTree() considers a path with 
>>> double backslash to be correct (return value 0), but the output is not 
>>> corrected as on MAC.
>>> 
>>> I have attached two scripts to show the behavior , amend to fit your 
>>> installation and have a try. I did not investigate on Linux/Unix.
>>> 
>>> 
>>> 
>>> 
>>> Hälsningar/Regards/Grüsse,
>>> P.O. Jonsson
>>> oor...@jonases.se 
>>> 
>>> 
>>> 
>>> 
>>> ___
>>> Oorexx-devel mailing list
>>> Oorexx-devel@lists.sourceforge.net 
>>> 
>>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel 
>>> 
>> 
>> ___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net 
>> 
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel 
>> 
> 
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel 
> 
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Question on SysFileTree()

[Rick McGuire]

Before the search, the name gets canonicalized. Things like double slashes
and  ".", and ".." directories get fixed up to get the fully resolved name
before processing the search.

Rick

On Thu, Feb 7, 2019 at 5:36 AM P.O. Jonsson  wrote:

> The fact that is „works“ is not a proof of it being valid. This is for me
> undefinded behaviour. In addition my point was that SysFileTree „corrected“
> my input, i.e. removed double slashes from the path.
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
>
>
>
>
> Am 07.02.2019 um 11:21 schrieb Enrico Sorichetti via Oorexx-devel <
> oorexx-devel@lists.sourceforge.net>:
>
> Dear P.O
>
> Having extra separators does not make a path invalid
>
> Just try with playing around with ls
>
> Just checked
>
> ls opt/ooRexx/bin///rexx
>
> ls opt/ooRexx/bin/
>
> E
>
>
>
>
> On 7 Feb 2019, at 11:09, P.O. Jonsson  wrote:
>
> Dear Developers,
>
> When working on modifying FileUtils.cls to work also for macOS/Darwin I
> used (by mistake, certainly) SysFileTree() with an invalid path and was
> astonished to see that it nevertheless produced a valid result. Is this
> intended?
>
> This is what I intended to do:
>
> *installDir = '/Users/po/Applications/ooRexx5.0.0‘*
> *name = 'rexx'*
> *j = SysFileTree(installDir'/bin/'name, f., 'FOS')*
>
> But instead I did (note the trailing slash)
>
> *installDir = '/Users/po/Applications/ooRexx5.0.0/‘*
> *name = 'rexx'*
> *j = SysFileTree(installDir'/bin/'name, f., 'FOS')*
>
> This produces a „//„ in the path, i.e. an illegal path
>
> Nevertheless SysFileTree() „corrected“ my input path, removed the
> additional slash and gave me the correct path back as f.1.
>
> I also tried on Windows and there SysFileTree() considers a path with
> double backslash to be correct (return value 0), but the output is not
> corrected as on MAC.
>
> I have attached two scripts to show the behavior , amend to fit your
> installation and have a try. I did not investigate on Linux/Unix.
>
> 
> 
>
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se
>
>
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Question on SysFileTree()

[P.O. Jonsson]

The fact that is „works“ is not a proof of it being valid. This is for me 
undefinded behaviour. In addition my point was that SysFileTree „corrected“ my 
input, i.e. removed double slashes from the path.

Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se




> Am 07.02.2019 um 11:21 schrieb Enrico Sorichetti via Oorexx-devel 
> :
> 
> Dear P.O
> 
> Having extra separators does not make a path invalid 
> 
> Just try with playing around with ls
> 
> Just checked 
> 
> ls opt/ooRexx/bin///rexx
> 
> ls opt/ooRexx/bin/
> 
> E
> 
> 
> 
> 
>> On 7 Feb 2019, at 11:09, P.O. Jonsson > > wrote:
>> 
>> Dear Developers,
>> 
>> When working on modifying FileUtils.cls to work also for macOS/Darwin I used 
>> (by mistake, certainly) SysFileTree() with an invalid path and was 
>> astonished to see that it nevertheless produced a valid result. Is this 
>> intended?
>> 
>> This is what I intended to do:
>> 
>> installDir = '/Users/po/Applications/ooRexx5.0.0‘
>> name = 'rexx'
>> j = SysFileTree(installDir'/bin/'name, f., 'FOS')
>> 
>> But instead I did (note the trailing slash)
>> 
>> installDir = '/Users/po/Applications/ooRexx5.0.0/‘
>> name = 'rexx'
>> j = SysFileTree(installDir'/bin/'name, f., 'FOS')
>> 
>> This produces a „//„ in the path, i.e. an illegal path
>> 
>> Nevertheless SysFileTree() „corrected“ my input path, removed the additional 
>> slash and gave me the correct path back as f.1.
>> 
>> I also tried on Windows and there SysFileTree() considers a path with double 
>> backslash to be correct (return value 0), but the output is not corrected as 
>> on MAC.
>> 
>> I have attached two scripts to show the behavior , amend to fit your 
>> installation and have a try. I did not investigate on Linux/Unix.
>> 
>> 
>> 
>> 
>> Hälsningar/Regards/Grüsse,
>> P.O. Jonsson
>> oor...@jonases.se 
>> 
>> 
>> 
>> 
>> ___
>> Oorexx-devel mailing list
>> Oorexx-devel@lists.sourceforge.net 
>> 
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
> 
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Question on SysFileTree()

[Enrico Sorichetti via Oorexx-devel]

Dear P.O

Having extra separators does not make a path invalid 

Just try with playing around with ls

Just checked 

ls opt/ooRexx/bin///rexx

ls opt/ooRexx/bin/

E




> On 7 Feb 2019, at 11:09, P.O. Jonsson  wrote:
> 
> Dear Developers,
> 
> When working on modifying FileUtils.cls to work also for macOS/Darwin I used 
> (by mistake, certainly) SysFileTree() with an invalid path and was astonished 
> to see that it nevertheless produced a valid result. Is this intended?
> 
> This is what I intended to do:
> 
> installDir = '/Users/po/Applications/ooRexx5.0.0‘
> name = 'rexx'
> j = SysFileTree(installDir'/bin/'name, f., 'FOS')
> 
> But instead I did (note the trailing slash)
> 
> installDir = '/Users/po/Applications/ooRexx5.0.0/‘
> name = 'rexx'
> j = SysFileTree(installDir'/bin/'name, f., 'FOS')
> 
> This produces a „//„ in the path, i.e. an illegal path
> 
> Nevertheless SysFileTree() „corrected“ my input path, removed the additional 
> slash and gave me the correct path back as f.1.
> 
> I also tried on Windows and there SysFileTree() considers a path with double 
> backslash to be correct (return value 0), but the output is not corrected as 
> on MAC.
> 
> I have attached two scripts to show the behavior , amend to fit your 
> installation and have a try. I did not investigate on Linux/Unix.
> 
> 
> 
> 
> Hälsningar/Regards/Grüsse,
> P.O. Jonsson
> oor...@jonases.se 
> 
> 
> 
> 
> ___
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel

___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

[Oorexx-devel] Question on SysFileTree()

[P.O. Jonsson]

Dear Developers,When working on modifying FileUtils.cls to work also for macOS/Darwin I used (by mistake, certainly) SysFileTree() with an invalid path and was astonished to see that it nevertheless produced a valid result. Is this intended?This is what I intended to do:installDir = '/Users/po/Applications/ooRexx5.0.0‘name = 'rexx'j = SysFileTree(installDir'/bin/'name, f., 'FOS')But instead I did (note the trailing slash)installDir = '/Users/po/Applications/ooRexx5.0.0/‘name = 'rexx'j = SysFileTree(installDir'/bin/'name, f., 'FOS')This produces a „//„ in the path, i.e. an illegal pathNevertheless SysFileTree() „corrected“ my input path, removed the additional slash and gave me the correct path back as f.1.I also tried on Windows and there SysFileTree() considers a path with double backslash to be correct (return value 0), but the output is not corrected as on MAC.I have attached two scripts to show the behavior , amend to fit your installation and have a try. I did not investigate on Linux/Unix.

Mactest.rex
Description: Binary data


Wintest.rex
Description: Binary data

Hälsningar/Regards/Grüsse,P.O. Jonssonoor...@jonases.se


___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel