Minor bug in edit-callers under lispworks;

   From: Alain Picard <[email protected]>
   Date: Fri, 27 Jun 2003 09:17:53 +1000

   Dear Maintainers,

   Please replace the function ilisp-source-files with the 
   definition below in lispworks.lisp v 1.9 (checked out yesterday)
   with the following.

Got it; thank you.

   The original doesn't appear to handle #P"/foo/bar" pathname syntax,
   hence the addition of the NAMESTRING around the pathname.
   If it _is_ supposed to handle the #P notation, then I think
   there is a bug in LISP-READ-CL-SYNTAX, as I get

   (lisp-read-cl-syntax "#P\"/tmp/foo.bar\"")
   ==>
   (\#P "/tmp/foo.bar")
   On which ilisp later barfs mightily.

lisp-read-cl-syntax is definitely not expected to deal with any "#"
reader macros, so I'm not surprised.  Ignoring #P would be possible, but
your fix is much cleaner.

   I have a weird déja-vu of having fixed exact same bug sometimes last
   year.  Weird.

That may well be, especially if you fixed it in elisp.  I mostly rewrote
the emacs end of the M-. code over the last half of last year, and
probably did not do a very good a job of integrating ongoing changes.
And I don't even have a copy of Lispworks to test, hence the bit rot.
:-/

   This also means that LW doesn't take advantage of the new M-. code,
because I couldn't port the Lisp end of the implementation to Lispworks.
The code is in find-src.lisp, if you (or anyone else) is willing to have
a go at it.  See also the edit-definitions-notes.text file.  It's
probably not a small job, but shouldn't be a huge one, either.

					-- Bob Rogers
					   http://rgrjr.dyndns.org/


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01