[comp.sys.xerox] ENOUGH-NAMESTRING bug

RTOR@UUNET.UU.NET (Owen Rees) (08/11/89)

Evaluating (CL:ENOUGH-NAMESTRING (CL:TRUENAME "filename")) for some file that
exists returns a string under Medley 1.0 but under 1.1 signals an error.  The
error is signalled under a string comparison function (CL:STRING-NOT-EQUAL if I
remember right - I can't check it at the moment because I am running ViewPoint
on the only machine which has been upgraded to 1.1).  One of the arguments is
the integer version number out of the pathname which does not get coerced to a
string.

Does anyone have a fix for this?

Owen Rees
APM Ltd
Cambridge UK