RExpression problems with named non-numeric vectors
RExpression seems to have a problem outputting named non-numeric vectors that is not present with named numeric vectors.
See attached workflow for examples.
#2 Updated by ben leinfelder about 11 years ago
I see this as the "token value" that is being used in the myput() function:
structure(c("alpha", "beta"), .Names = c("a", "b"))
We currently aren't handling tokens that start with "structure...."
Seems like this could be a record token - but I'm open to suggestions.
#3 Updated by Oliver Soong about 11 years ago
The structure is in place to preserve attribute data and such. Since RExpression is already dumping attribute data for numeric vectors, it wouldn't be a stretch to have it do that for other simple vectors (character and logical). We still have the problem that we've always had of dropping useful information (names, dimensions, and such). The proper alternative is to correctly handle the passing of attribute data, but that leads us into that whole RObject business (which could be done through Records and toggled with an actor parameter, but is more work than I think anybody has time for at the moment).
Here's my suggestion. If it's a special data type (data.frame, list, factor, etc.), then handle with whatever special handling we already have. If it's a basic data type (character, logical, or numeric), then insert "attributes(data) <- NULL" prior to attempting to export. That should dump all the stuff Kepler can't handle.