Chip Davis wrote:
> I'm with Klass on this one, Rony.  And you really should avoid 
> case-sensitivity 
> as well.
>
> There are only three pieces of information that the extension must convey: 
> 'Rexx', 'BSF4Rexx(Java)', and 'OpenOffice'.  It's not necessary to specify 
> that 
> it is "Open Object" Rexx, since that's the only "Rexx" that is applicable.  
> By 
> the same token, "BSF4Rexx" is a tad more obscure than "Java", so "Java" would 
> be 
> a more valuable identifier.
>
> One suggestion would be simply '.jro', except that there is too great a 
> possibility that it will collide with another extension in the Java 
> namespace. 
> In fact, the proliferation of Java application files is making it difficult 
> to 
> assign with confidence any extension that starts with '.j'.
>
> Besides, I feel that the beginning of the extension should indicate the 
> source 
> language of the file.
>   
Good point too!
> For that reason, I would suggest that all BSF4Rexx ooRexx programs use a 
> '.rxj*' 
> extension.  After all, the whole point is that the code is written in Rexx, 
> not 
> Java, for the Java environment.  The 'j' identifies the file as input to the 
> BSF4Rexx Java interface, and further suffixes would identify the application 
> environment to which the program communicates.
>
> Thus, an ooRexx program that simply interfaces the Java virtual machine would 
> have an extension of '.rxj'.  This extension is not likely to be used by 
> anything else. (Fortunately, NetRexx uses '.nrx'. ;-)
>
> An ooRexx program that uses the BSF4Rexx Java framework to access OpenOffice 
> would have an extension of '.rxjo' (or '.rxjoo' if you're concerned about 
> application namespace collisions with only one letter).  One which accesses 
> SQL 
> would be '.rxjs', '.rxjsq', or even '.rxjsql'.  The suffix characters are 
> where 
> you want to have the ability to disambiguate a multitude of target 
> applications.
>   
O.K. so we would have: ".rxj", ".rxjo".

Currently, an extension of ".jrexx" is being used on the MacOSX.
Following your intriguing logic this naming scheme could be extended for
OOo scripts using ".jrexxo".

Of course, using "r" for rexx as the first letter would yield maybe
".rexxj" and ".rexxjo", if too long shortening it to ".rexj" and
".rexjo", finally shortening to arrive to your suggestion ".rxj" and
".rxjo".

Hmm, how about the following questionnaire table of possible Rexx script
extensions for BSF4Rexx and OpenOffice-Rexx programs?

*Please check
*       *Extensions for BSF4Rexx programs (interfacing with Java)
*       *Extension for OpenOffice-Rexx programs
*

        .rxj
        .rxjo

        .rexj
        .rexjo

        .rexxj
        .rexxjo

        .jrexx
        .jrexxo


Please just pick any one line, no matter whether you are using
BSF4Rexx/OOo or not, just to learn what you associate the best. And if
you would like to append two 'o' for the OpenOffice-Rexx scripts, please
indicate so.

> Orthographically yours,
>   
8-))

Thank you (and Klaas) for your feedback and efforts !

---rony



------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to