http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5722
Christopher Brooks <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Christopher Brooks <[email protected]> --- The issue here is that if the record field names are not well-formed strings, then it is not possible to create such a record using a string. This came up when we tried to use the Test actor with a record that had a field name. One alternative would be to change the syntax of the record field so that spaces and other characters would be permitted. Unfortunately, the parser started getting conflicts if I use {"field with space" = "foo"} In either RecordAssembler or RecordDisassembler, my workaround was to check for a port that matched the field name. If none was found, then to try substituting spaces for any underscores. This is gross, but worked. The problem is that arbitrary field names are not going to work as they did before, the spaces and other characters will be converted to underscores. -- You are receiving this mail because: You are the QA Contact for the bug.
_______________________________________________ Kepler-dev mailing list [email protected] http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
