[kepler-dev] [Bug 3962] - RExpression2 - support RecordTokens with length=1

bugzilla-daemon at ecoinformatics.org bugzilla-daemon at ecoinformatics.org
Mon Apr 13 15:13:44 PDT 2009


http://bugzilla.ecoinformatics.org/show_bug.cgi?id=3962


leinfelder at nceas.ucsb.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Comment #3 from leinfelder at nceas.ucsb.edu  2009-04-13 15:13 -------
RExpression2 actor now accepts the length=1 RecordToken, but slightly mutates
the structure during the conversion.
Ptolemy -> JRI -> Ptolemy results in the following Token:
{a = {1}, b = "b", c = {3}}
Notice that the the numeric tokens (a and c) are now lists, whereas the string
token is a single token.
JRI _only_ assigns numeric values using arrays of them. Even treating the
String as a String[] doesn't force "b" to be a list - this seems like a JRI
limitation.

I think we can live with what's returned. The alternative is to treat the
numbers as strings so that it's a uniform data structure.

Subsequent passes through multiple RExpression2 actors preserves the data
structure as such:
{a = {1}, b = "b", c = {3}}
so at least it's predictable from that standpoint.


More information about the Kepler-dev mailing list