|
From: Daniel J S. <dan...@ie...> - 2006-03-05 09:02:54
|
Ethan A Merritt wrote: > On Saturday 04 March 2006 12:45 pm, Petr Mikulik wrote: > >>Ah, these in addition: > > > Unfortunately, I don't understand the codepath for reading > binary files well enough to back out of these failures cleanly. > At the time the message is printed, we are several routines > deep in the binary file code. I think you would have to > add error return codes to each layer of routines, and > error-handling code at all the call sites. > > Maybe Daniel would be willing to take a look at it > after I sort out the normal [ascii] input file case. > It was his code originally, I think. > > >>gnuplot> plot 'xxx' binary filetype=edf with image >> Can't open data file "xxx" >> util.c: No such file or directory >>gnuplot> plot 'xxx' binary filetype=avs with image >> Can't open data file "xxx" >> util.c: No such file or directory >> >>gnuplot> plot 'demo.edfxxx' binary filetype=auto with image >> ^ >> Unsupported file type I waited for a delayed gnuplot-beta-list email to appear on this, but nothing has arrived. I don't fully follow the issue here. Is there a problem recognizing some file in the present working directory? The above first two complaints are indicating that. The third complaint is that the file type is to be recognized automatically. Gnuplot makes this decision based only upon the file extension. So, 'edf' is in the table of "extension to function pointer" mappings, but 'edfxxx' isn't. If we want to have something where gnuplot will also search into the file itself and look for keys about type, then we'd probably have to add another function pointer in the table containing a function that does the searching in addition to the one that handles parameter settings for the file. Dan |