lisp-slashify should bind print-escape-newlines nil

   From: Daniel Barlow <[email protected]>
   Date: Tue, 05 Aug 2003 02:33:49 +0100

   Every so often when I use compile-defun-lisp or similar commands to do
   something to the form at point, I get strange error messages along the
   lines of this one . . .

   By inserting calls to (message string) in lisp-send-region, I was able
   to see that it's sending e.g.

   (ilisp:ilisp-compile "(sql:def-view-class year-end-transaction (transaction)\n  ()\n  (:base-table \"rm_transaction\"))" "ROSEMARY" "/home/dan/src/telent/rosemary/transaction-class.lisp")

   to the inferior lisp.  \n in a CL string is read as the 'n' character,
   of course.  To cut a long story short, something somewhere in my emacs
   had trodden on print-escape-newlines, which causes the prin1-to-string
   in lisp-slashify to produce CL-incompatible output.  I think
   lisp-slashify should bind printer control variables such as this if it
   expects anything from the output.

   Thanks to ohler on #lisp for helping to track this down.

   - -dan

   - -- 

Point well taken.  Of course, it's rude of whatever-it-is to trash the
print-escape-newlines value, but ilisp needs to be robust about such
things.  Patch imminent.

					-- 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/psa00100003ave/direct;at.aspnet_072303_01/01