Records.hh should include a define statement, denoting the different available file types:

define EVENTLISTFILE /xxx/yyy/templates/evl/1.0.0/eventlistfile.tpl

Not yet sure how to implement this. Could add another index file, e.g., files.tpl? But then one would need to introduce some extra syntax, e.g.,

EVENTLIST eventlist.tpl

Or implement a scheme based on tpl file names? That seems more elegant, e.g., eventlist.file.tpl, and telconfig.include.tpl.

Or more general, do we need some sort of configure script?

So that that the template files can be used with cfitsio without cluttered comments.

How should we deal with optional table entries? We could have different tpl files, one that includes them, one that doesn't and then have a FITSRecord for each.

Currently there is an ExtraRec struct, which can be added to the base struct. Reading such a structure from FITS tpl files seems difficult and would require additinal control key words (e.g. \optstart \optend) and then large changes to the evlio.template data structures.

How should different versions of format being handled?

(1) One library/include per version?
(2) Ads version to dicts name and bundle them all into one library?

Array table columns are not yet supported in FITSRecord output. This needs to be fixed.

Correct example using the predefined Records.

Makefile should run the appropriate python scripts to build the headers and then compile the library.