<tag>
some-variable-character
</tag>
and to read a vector of three real numbers as
<tag>1. 2. 3.</tag>
(as written by FoX and wxml.f90) in addition to the usual case
<tag>
1. 2. 3.
</tag>
Make the behavior of new UPF reading code more tolerant:
- If an incorrect number is found in an attribute, do not crash: issue a
warning and set the attribute value as if the attribute was not found
- Do not check actual index vs the "index" attribute for v2 UPF files:
the previous code didn't do that, I think, didn't crash if index missing
Writing a long vector with free format (*) may result in very long lines,
exceeding the current 1024 character limit for reading, set in xmltools.f90.
Out od the two possible workarounds: limit the number of data per write, or
use an explicit format, the latter was chosen. The formats used for write,
I18 for integers, es24.15 for reals, should guarantee no loss of precision.
Fixes issue #222
- can read tags not in order, although only in some specific cases (luckily
including those PP files that do have some tags not in the usual order)
- writes complex variables as two reals, not in fortran free format:
it makes reading data from other languages (e.g., python) easy