| 1 |
This file contains a list of known bugs in NXtranslate or one of the |
| 2 |
libraries it depends on. Being smart about how you write your |
| 3 |
translation file will be able to avoid most of them. |
| 4 |
|
| 5 |
OPENING A NEXUS FILE MULTIPLE TIMES - There is an inconsistent bug in |
| 6 |
the NeXus API (napi) where the library will crash if a NeXus file is |
| 7 |
opened for read, closed, then opened for reading again. I have been |
| 8 |
unable to reproduce it in a sample code to submit to the NeXus |
| 9 |
developers. |
| 10 |
|
| 11 |
LINKING TO A ROOT GROUP - Creating a link to a group that exists at |
| 12 |
the root level (e.g. a NXentry) will move the group, not create a |
| 13 |
copy. If the link is at the same level, just inside the root, the |
| 14 |
group will be renamed. If the link is somewhere else in hierarchy the |
| 15 |
group will be moved to that point. |
| 16 |
|
| 17 |
RETURNING AN EMPTY TREE - The retrievers are assumed that they add at |
| 18 |
least one Node to the tree they are given for population. If they do |
| 19 |
not the xml_parser will crash. The user cannot create this error, only |
| 20 |
a programmer can. Instead of returning an empty tree the Retriever |
| 21 |
should throw an exception (invalid_argument, runtime_error, or |
| 22 |
exception) to notify xml_parser of the extraordinary call. |