> I'd be reluctant to add such a fix at this late stage, but if it is the
> cause of this problem, and the DosFileDirFullName problem did not exist
> in 3.6, it might be important enough to tack on to the 3.7 final
> stream.  (As evidenced by two different people posting about the same
> bug when asked to test today.)

Holy bureaucracy. Something is really screwed up here. This fix is a)
critical b) three lines long c) comes with a whole set of tests d) was
reviewed e) was even approved ... and it took us from april (when I first
posted the fix) to september to /not/ fix it? Anyone besides me thinking
that there is something Really Wrong with the process?

Anyways - Doug, *please* include the fix regardless of any late stage. The
fix is the counterpart for the changes in DosFileDir>>splitName:to: (these
logically belong together) as the tests will easily illustrate (3.6 didn't
have this particular problem but it had others which were equally severe).

Cheers,
  - Andreas