There are enough different ways that data can be provided
for PDL processing that it would be *very* helpful if we had
an IO wizard to simplify figuring out the best way to read/write
a given file or certain data.
It would need to be more than file name suffix magic
as some of the PDL IO routines are determined by
the content of the file (text, binary, numbers, with
non-numbers, columns, CSV, ...).
It would be nice if it could produce command strings,
link/show documentation, or even transparently
"do the right thing" when it can be correctly known
from the given info.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This feature could also go with the long considered review of the PDL IO interfaces and method naming schemes to regularize argument orders and routine names to be more consistent. It would be nice not to have to guess whether the filename/filehandle goes first or last,...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are you thinking of something more than just filename suffix magic, or would that suffice?
It would need to be more than file name suffix magic
as some of the PDL IO routines are determined by
the content of the file (text, binary, numbers, with
non-numbers, columns, CSV, ...).
It would be nice if it could produce command strings,
link/show documentation, or even transparently
"do the right thing" when it can be correctly known
from the given info.
This feature could also go with the long considered review of the PDL IO interfaces and method naming schemes to regularize argument orders and routine names to be more consistent. It would be nice not to have to guess whether the filename/filehandle goes first or last,...