iraf.net

Is there a maximum length for strings as parameter values in tasks?
We have a list of file names which seems to be too long for epar, dpar, and lpar. The value can be set on the command line, and the task uses all of the files on the list, but when you try to dump or edit the parameter file, the value is given as a null string, without even quotation marks. The value in the parameter file in UPARM$ is correct, however, unless you write out from the abortive epar, which replaces everything after the long string (of file names separated by commas) with the default values. Could it be the commas in the value?-Doug

Doug,It depends somewhat on the type of the param and what field you're talking about, e.g. list and pset structs are SZ_FNAME (255), strings can be as long as SZ_LINE (1023), but the p_min field used for enumerated lists is limited to 160 chars. Is there some reason you're not using an @-file for a long list of filenames?-Mike

[quote:3862c3e4f9="fitz"]Is there some reason you're not using an @-file for a long list of filenames?
-Mike[/quote:3862c3e4f9]The list started small and grew. The list of templates that causes the problem
is only 115 characters long and is being read into a variable with the length SZ_PATH, so length shouldn't be a problem. There are 7 commas in it.We are going to use @filelist, but thought you should know that something unusual is happening.-Doug

Doug,Please post a reproducible example.-Mike