Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Another new (2012-04-20) beta version for BSF4ooRexx available

5 views
Skip to first unread message

Rony

unread,
Apr 20, 2012, 11:16:41 AM4/20/12
to
Hi there,

today, I created a new beta for BSF4ooRexx, which you can download from
<https://sourceforge.net/projects/bsf4oorexx/files/beta/20120420/>. It incorporates all fixes as of
today, AFAICT there are no open bugs anymore, ooRexxTry.rxj got improved a little bit more.

Best regards,

---rony



On 12.03.2012 18:49, Rony G. Flatscher wrote:
> Today, a new version of the current beta for BSF4ooRexx has been created, that adds the following
changes:
>
> the NetRexx datatype "netrexx.lang.Rexx" is now being honored in the new Rexx handlers the way
it has been implemented in BSF4ooRexx for many years already (NetRexx types will be translated to
Rexx strings transparently),
>
> as in a process there can be any number of Rexx programs executed in separate Rexx interpreter
instances, now BSF4ooRexx manages the supportive use of requiring BSF.CLS per Rexx interpreter
instance (used to be globally); this means that in one Rexx interpreter instance one can use the
external Rexx function BSF() without the camouflaging support of BSF.CLS, while in another Rexx
interpreter instance the camouflaging support may be used.
> [Don't worry, if this is still not really clear, just attend the ucpoming International Rexx
symposium to learn more, if interested in this aspect! :-) ]
>
> Please note, the reply-to has been set to the BSF4ooRexx developer list
"bsf4oore...@lists.sourceforge.net".
>
> ---rony
>
>
>
> On 25.02.2012 21:04, Rony G. Flatscher wrote:
>> There is a new version of BSF4ooRexx available on sourceforge:
<https://sourceforge.net/projects/bsf4oorexx/files/beta/20120225/> with accompanying Java
documentation (in form of zip-archives).
>>
>> New features to test:
>>
>> configuring an ooRexx interpreter instance from Java (e.g. adding paths, extensions, command
handlers, exit handlers),
>> implementing Rexx command handlers in Java,
>> implementing Rexx exit handlers in Java,
>> making a subset of the ooRexx APIs directly available to Java implemented Rexx command
handlers and Rexx exit handlers that allow e.g. to get/set Rexx variables etc.
>>
>> After installation of this package (just follow the readme in "readmeBSF4ooRexx.txt") you may
want to check out the new samples highlighting/demonstrating these new features in
"samples/Java/handlers".
>>
>> Documentation of these rather low-level ooRexx features are given best by the ooRexx programming
guide "rexxpg.pdf" itself.
>> [Also you might consider to attend the upcoming International Rexx symposium in May (14-16) in
North Carolina (RTP) to learn about and discuss these new features making the very core of ooRexx
available to Java/NetRexx programmers to exploit and opening up new possibilities.]
>>
>> Please direct questions to the BSF4ooRexx mailing lists (although I will monitor also the ooRexx
list) at <https://sourceforge.net/mail/?group_id=400586>.
>>
>> If you find problems/bugs, then please file them with the BSF4ooRexx bug tracker at:
<https://sourceforge.net/tracker/?group_id=400586&atid=1660873>.
>>
>> ---
>>
>> Please note, if you are an author or have access ot applications written in Java/NetRexx: which
possess command window interfaces for users to type commands (like editor commands, database
commands and the like) to the Java/NetRexx applications, then please consider to add Rexx subcommand
handling support by exploiting these new features! It is very easy, simple, but adds a lot of power,
the Rexx way ...
>> :)
>>
>> ---rony

0 new messages