Tuesday, March 25, 2003 Hans Hagen wrote: HH> At 11:38 AM 3/25/2003 +0100, you wrote:
>>The third point is too severe in its behaviour: it's a good thing that >>circular >>loading is prevented, but this shouldn't prevent inclusion of >>other files with different extensions! After the removal of the >>\jobsuffix extension, inclusion should go on normally! HH> it will, fo rthose sufixes that are recognized as being supported by the HH> backend; numbers are special case in the sense that they don't relate to a HH> file format; if you uncomment the lines i mentioned you get them supported The problem is not the numbers as such, it's a more general point; especially then type= or method= are specified, extension should be irrelevant as long as it doesn't cause name clash. On a very general basis, I would say that the best approach would be: Step 1: check for name clashes: * if name = \jobname: (a) if extension = \jobsuffix or output suffix (dvi, pdf), quit parsing (b) if no extension, remove jobsuffix and output suffix from list of searched extensions. Step 2: if extension is specified, and no method is specified, set method to the one associated with this extension, if there is one. Step 3: check if file exists; * if we have a full name, try to open the specified name.extension, with the specified method * if the file is not found, and no extension was specified, look for all the known extensions (except the ones forbidden by Step 1, point b); if a method/type is specified and it has a default extension, start looking from that extension Or something like this ... -- Giuseppe "Oblomov" Bilotta _______________________________________________ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
