From: Gil B. <gi...@be...> - 2007-12-01 18:44:59
|
Other than the obvious (but very descriptive) .REX, I've seen (and used) .FRM for "frameworks"; e.g. SOCKETS.FRM. Mark Miesfeld wrote: > On Nov 30, 2007 8:44 AM, David Ashley <da...@us...> wrote: > > >>I added a new file (ooRexxUnit.cls) to the trunk of the SVN test tree. This >>is just a rough outline (it sure as heck doesn't work yet!) of some things >>that can be improved over the old class. Here are some of the major points. >> >>1. There is only one class in the class file. > > > ::class 'ooRexxUnit' public > > This is another thing I don't quite follow. Conceptually, ooRexxUnit > is not a class but a framework. It is modeled after JUnit. JUnit is > also, conceptually, not a single class but a framework. There is no > JUnit class. > > Originally the ooRexxUnit framework was contained entirely in one > file, which happened to be called ooRexxUnit.cls. Now, in hindsight, > the .cls extension may not have been correct. But, on the other hand, > I don't think we have any clear-cut convention in ooRexx as to what it > should be. > > * In redesigning the TestCase class, I'm not sure that the class name > should be changed. > > * If the class name is changed, which maybe is justifiable, then I > don't think it should be changed to ooRexxUnit. > > * If the .cls extension is wrong for a file that contains more than > just classess, as ooRexxUnit.cls does, then what extension should we > use for files in the ooRexxUnit framework? > > -- > Mark Miesfeld > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > -- Gil Barmwater |