Hello Mark and Rick,
> As Rick said, the errors you saw in the RexxQueue test are due to
> installing the test suite in a directory with spaces in the name, not due
> to rxapi.
>
> It never occurs to me that someone would voluntarily install any thing
> is a directory with spaces in the path name. I'll add a note to the test
> suite doc that you can't do that and expect valid results.
Honestly, Mark, it never - ever - crossed my mind the test suite wouldn't
support one or more space in the directory path. I also feel it is a
mistake to "add a note to the test suite doc that you can't do that and
expect valid results." At the same time, I ALSO respect your right (as the
developer) to take the note route and not support spaces. Yet, it is my
hope a discussion can start on the topic and (in time) it will convince you
and / or Rick to support spaces in both the path and file names of ooTest
and its many test cases (supplied by you and users).
As Chip Davis started this discussion, let me add to it with my input:
I completely agree with Chip Davis. Spaces are a fact of life for Windows
users in their directory path, file names, and maybe even file extensions.
This is also true for other operating systems ooRexx supports. In addition
to spaces, there are special characters, too. ooRexx, itself, already
supports various combinations for directories and files. The ooTest suite
should do it, too.
At this point, there are many directions I can take in the discussion and
hope the path I take works. Please bare with me while I try to cover
various aspects of the subject.
*NEVER CROSSED MY MIND:*
Why did I say: "Mark, it never - ever - crossed my mind the test suite
wouldn't support one or more space in the directory path?" I said it for a
couple of reasons:
1. ooRexx, itself, already supports spaces as part of its own directory
and file names access/support. Thus the standard for the product is to
support it.
2. Placing the test suite inside the ooRexx directory does make sense,
as it is a good way to organize your files (programs and data).
3. From a personal perspective, I resist putting anything more than
necessary into the root directory of my boot drive. If the OS puts it
there, fine, but otherwise I try to avoid it.
4. User supplied test cases could include, as part of the test, spaces
in its directories, file name and/or extensions.
5. Plus there should be test to insure ooRexx, itself, didn't lose its
own ability to support spaces.
*UPDATING OOTEST:*
Unlike Chris, I don't (yet) see why fixing the test case program to support
spaces in directories and name is infeasible.
I admit, I haven't looked at the ooTest code but it is just code after
all. If you can see how to do it, you can code, right?
IMHO, programmers should have path and file name support in their toolkit
(subroutines for procedural code and methods for object oriented). This
way a programmer only codes this support once, tests it with each program
that uses it, and benefits from reusing his or the code of another person.
It wouldn't surprise me to learn you or Rick already have a directory /
file name subroutine / method in a toolkit and it is available for you to
use with ooTest.
*FUTURE*:
Finally, you're wanting people to use the test cases. I don't know about
Chris, but I have an interest is running the test suite and even adding my
own tests (mostly procedural for now) in time. I'm hoping I won't have to
limit my testing, but instead be able to test what ooRexx supports (all of
it).
*ACCEPTANCE:*
I accept space aren't there today, but am hoping to hear spaces will work
in the "near" future.
Thank you and again thank you for give us ooRexx!! You obviously love it
greatly!
Bert Moshier
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.
------------------------------------------------------------------------------
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
