Square brackets are just a method, not restricted to just collection
classes. Any class can choose to implement that method, so this problem is
no different than determining the effect of any method call.
Rick
On Mon, Oct 20, 2014 at 5:57 AM, Rony G. Flatscher
wrote:
> It seems that 5.0 will s
It seems that 5.0 will supply square brackets to call a routine object. Why is
this?
Square brackets have been in ooRexx for a long time and have been used for
accessing collections.
Making square brackets call a routine object somehow breaks that
collection-related notion, and
seems a little b
The annotations must consist of name/value pairs, and that is the only
thing that is going to be provided.
Rick
On Mon, Oct 20, 2014 at 5:45 AM, Rony G. Flatscher
wrote:
> It is really great that annotations get added to the language!
>
> It may be conceivable that there are annotations that co
Nothing is currently planned in 5.0.0 for making any of that information
available. That stuff is the purposes of the interpreter to determine if
the package can be loaded.
Rick
On Mon, Oct 20, 2014 at 5:40 AM, Rony G. Flatscher
wrote:
> The RexxPackageEntry structure has a few fields that mi
It is really great that annotations get added to the language!
It may be conceivable that there are annotations that consist of many
field/value pairs, but also of
field-names only (like "deprecated" or "testmethod", which in junit allows one
to annotate methods
to be testmethods even if they do
The RexxPackageEntry structure has a few fields that might be interesting for
Rexx programs:
* apiVersion
* requiredVersion
* packageName
* packageVersion
* loader and unloader (whether they exist at all)
* routines
* methods
Will 5.0 allow for retrieving these values (maybe via ex
