On Saturday 15 February 2014 12:58:28 Bertram Moshier wrote:
> P.S. *THOUGHT / SUGGESTION* for ooRexx: ooRexx (both procedural and oo)
> needs a "base" function / method to make supporting paths and file names
> regardless of form easy. By this I mean: Give ooRexx programmers ability
> to process files without worrying about the format or composition of the
> directory or file name.
> The benefit of having a centralized source handling the directory / file
> names would:
>
> - Enhance portability of Rexx code,
> - Reduce the
> - amount of coding
> - complexity of code
> - chance for errors
>
> of all Rexx programs. It would make worrying about spaces, special
> characters, etc a thing of the past for everyone, when it comes to
> directories and file names, and extensions. Of course, the programmer
> would need to use these functions / methods, but such is true for every
> programming effort.
>
> In the end, adding this function / method would also aid you in your own
> Rexx programming, regardless of the operating system.
I may be wrong, but doesn't the definition of "special" characters in
directory and file names depend on the filesystem type in use? E.g. VFAT vs.
ext vs. reiser vs. xfs vs. hfs ..., each of which have their own rules about
what is considered a "special" character.
Leslie
------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Oorexx-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-users
