[360] in SIPB bug reports
Re: No Deal
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Wed Mar 8 20:10:47 1989
Date: Wed, 8 Mar 89 20:09:25 EST
From: Ken Raeburn <raeburn@ATHENA.MIT.EDU>
To: Bill Sommerfeld <wesommer@ATHENA.MIT.EDU>
Cc: <amgreene@ATHENA.MIT.EDU>, bjaspan@ATHENA.MIT.EDU, bug-sipb@ATHENA.MIT.EDU
In-Reply-To: Bill Sommerfeld's message of Wed, 8 Mar 89 00:27:13 EST,
My vote would be to assume the '.tex' suffix.
Moreover, the fact that the code has '.' hard-coded as the separator
character is itself an indication of a lack of portability; both ITS
and VM/CMS use ' ', not '.', as a separator character in filenames.
However, at least some implementations of C libraries under VM/CMS do
use '.' as the separator. The FTP software does this as well.
However, you effectively get only one. The name "FOO.TEX.A" describes
file name "FOO", type "TEX", minidisk "A"; you can't play games with
the minidisk tag, really.
So, if I name two files "foo.bar.tex" and "foo.quux.tex", they'll both
use a \jobname of "foo"? THIS IS ALSO BROKEN. At the very least, it
should look up to the point of the _LAST_ period, not the _FIRST_
period.
This is approximately what I would want to see.
The reasonable behavior would seem to me to be using the full name as
supplied, with the .tex suffix appended if not already present. Then
strip off that suffix (from the last period, not the first) and
replace it with .dvi &c as needed.
If I have two files "foo" and "foo.tex", what happens if I run tex on
them (in the case where the suffix isn't required)? You can't
completely get around the problem of files overwriting one another if
suffixes are optional.
_kr
