FIELD_N_NAME and FIELD_N_FILL in table objects


I'd like to know if it could represent a big problem of compatibility to
stop writing the FIELD_N_NAME and FIELD_N_FILL (being N the number of
the column) attributes in table objects for the HDF5 Table API.

I'd like to stop writing these attrs for PyTables Table objects that
closely follows the above high level API, mainly because they take a lot
of time to write/copy when there are a lot of columns in a table.

My understanding is that this info can be retrieved by introspecting the
HDF5 type ID, but I'm not sure about the effects of removing these attrs
when using other tools that also adheres to the HDF5 Table API.



Francesc Alted