On Jan 29, 2008 10:58 AM, Mark Miesfeld <miesfeld@gmail.com> wrote:
On Jan 28, 2008 7:53 AM, Rick McGuire <object.rexx@gmail.com> wrote:
> The new APIs I've been working are going to borrow some features from the
> Java JNI interface. ...

> The extension list is another matter entirely.  I'm not sure there's a
> platform convention to be used here, though the same convention as the
> search patch might make sense.

The convention on Windows is to use the ';' character.  But that
doesn't need to be followed.

And unix systems use the ":" character, which is why I'd like to punt on that one and just pass it through to the code that really needs to use it. 

Rick

 


> For efficiently, it might be nice to parse
> this list into a list of extensions once, rather than reparse it each time
> an external call is made.  In that case, having a portable syntax would make
> life easier.  Separating the strings with ",", " ", ";', or ":' might all
> make sense.  I'm really easier here, though I think "," or " " would be
> better since they wouldn't get as confused with the format of the search
> path.

That makes sense to me, to use something other than the search path
format.  When you say 'list' I think commas.  So, a comma seems the
best choice to me.

--
Mark Miesfeld

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel