Help save net neutrality! Learn more.

#25 sysfiletree problem



When running my OREXX 2.1.3 scripts on Windows XP
sysfiletree returns a different result compared to
1.0.3 on Windows NT.

The statement is:
call sysfiletree 'STDWS.', 'resultstem.', 'FO'

On Windows NT with 1.0.3 the file STDWS was returned in
the resultstem but when running the same statement with
2.1.2 on XP no file was found.

On Windows this is not the right behavior, copied from

If no file name extension is specified in the
lpFileName parameter, the default library extension
.dll is appended. However, the file name string can
include a trailing point character (.) to indicate that
the module name has no extension.

I hope this incompatibility will be fixed with ooREXX 3.0.

Kind regards, Gert


  • Mark Miesfeld

    Mark Miesfeld - 2009-07-07


    Not sure if you are still following this, but in case you are:

    The section you quote from MSDN pertains specifically to an argument passed to the LoadLibrary() API. This really has no bearing on how the file system behaves or how SysFileTree() should behave.

    Nevertheless, it seems to me that expecting SysFileTree() to behave reasonably close to the dir command on Windows is justifiable. And in fact dir will return a STDWS file if you specify it as STDWS with a dot on the end:

    C:\work.ooRexx>touch STDWS

    C:\work.ooRexx>dir STDWS.
    Volume in drive C has no label.
    Volume Serial Number is BC89-B386

    Directory of C:\work.ooRexx

    07/07/2009 01:59 PM 0 STDWS
    1 File(s) 0 bytes
    0 Dir(s) 68,976,734,208 bytes free


    So, in order to resolve this bug, I'll fix that behavior.

  • Mark Miesfeld

    Mark Miesfeld - 2009-07-07

    Gert, haven't seen any activity from you for some time. Hope you haven't given up on ooRexx. <grin> Sorry it has taken so long to resolve the bugs you opened.

    Committed revision 4886.

  • Mark Miesfeld

    Mark Miesfeld - 2010-02-23

    Committed revision 5595.
    4.0.1 merge.



Cancel  Add attachments