starting with 2005-06-05, brief infos about changes are recorded in here, ---rgf


-------------------------------------- 2005-06- 05 ----------------------------------
changes of 2005-06-05 version, --rgf

- BSF.CLS: renamed all BSF-pass-through class methods to start with "BSF."; this
           way it is always clear that the BSF4Rexx interfaces are addressed

           BSF-class methods: name changes
           -------------------------------

           createArray          --> bsf.createArray
           exit                 --> bsf.exit
           getStaticValue       --> bsf.getStaticValue
           getStaticValueStrict --> bsf.getStaticValueStrict
           import               --> bsf.import
           lookupBean           --> bsf.lookupBean
           pollEventText        --> bsf.pollEventText
           postEventText        --> bsf.postEventText
           setRexxNullString    --> bsf.setRexxNullString
           sleep                --> bsf.sleep
           wrapArray            --> bsf.wrapArray
           wrapEnumeration      --> bsf.wrapEnumeration


- BSF.CLS: BSF-class method "bsf.import": change in the order of arguments!
           ----------------------------------------------------------------

           Arguments got switched, "RexxName" argument is now optional:

              import(RexxName, JavaFullClassName)

           was changed to:

              bsf.import(JavaFullClassName [, RexxName])

           If "RexxName" is not given, then the created BSF Java class object proxy
           proxy is not saved in .local; hence creating Java objects with it is only
           possible by sending NEW and NEWSTRICT to the variable which stores the
           reference to it (otherwise the class object would be stored in .local and
           could get accessed like any other ooRexx class via its environment symbol
           ".RexxName")

- BSF.CLS: all imported Java classes can be instantiated with "newStrict()", which
           allows indicating the datatype in front of every argument, if necessary

- BSF.CLS: sending messages to the BSF Java class object proxy now behaves the same
           as sending ooRexx messages to BSF Java object proxies: the (static) methods
           are resolved and dispatched; hence no need to instantiae a Java class just
           to get at its static methods (or static fields for that matter)

- The "test" and "sample" Rexx programs have been updated accordingly.