Starlib: Known Bugs
This is a list of some of the known bugs and "features" of
starlib. Please check here before e-mailing any bug reports
to the starlib maintainer (that would be me).
Bug List
-
global_: The handling of the
global_
keyword
is not correct when more than one global_
keyword
exists in the file. As of right now, there is no relationship
between saveframes and datablocks and the global tags that
were in effect when they were read in. The starlib in-memory
representation of a global_ block only allows one such block
to exist for an entire file. If more than one global_ block
is encountered, then both are concatenated into one global_
block in memory, with no record of which global_ parameters
were in effect at what point in the file.
-
duplicate names: Right now there is no double-checking
to ensure that the STAR file has no duplicatated names. For
example, it is possible to have two tags with the same name
in the same saveframe. It is also possible to have two
saveframes with the same name, and two datablocks with the
same name. Putting this check in place would greatly slow
down the insertion of new nodes to the star tree, since each
insertion would require that there be a check for duplicate
names, and each time a tag is renamed, a similar check would
be needed.
- previous topic -
- next topic -