gcl-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gcl-devel] XP - ansi pprint


From: Peter Wood
Subject: Re: [Gcl-devel] XP - ansi pprint
Date: Tue, 27 Aug 2002 14:57:58 +0200
User-agent: Mutt/1.4i

Hi

On Mon, Aug 26, 2002 at 11:47:50PM -0400, Camm Maguire wrote:
> Greetings, and thanks for the suggestion!
> 
> I've downloaded the code, and it would seem pretty straightforward to
> include.
> 
> 1) I compiled xp-code, loaded xp-tests and eval'ed do-tests.  I got
>    one error with my local tree fixing some dotted list problems.
>    I'd like to see your test output.
> 

I have attached it.

> 2) I cannot seem to compile xpx-code.lisp, as one of the format
>    strings cannot be coerced to the designated destination type.
> 

I get this error:

Error in CONDITIONS::CLCS-LOAD [or a callee]: "~:<address@hidden, ~_~}~:>" 
cannot be coerced to a pathname.

And at a _guess_, I would say it might have something to do with Gcl's
pathname system.??

> 3) I'm a bit unclear on how the integration should take place.  What
>    about the parameters in xp-install?  :pkg cl-user?  :macro?  I
>    take it shadow should be the default 't.  So just '(load
>    "xp-code.lisp")(xp::install ...)(save-system foo)', then run foo
>    with '(load "xp-test.lisp")(do-tests)'?  Is xpx needed?  Can
>    cp-code just be compiled and loaded without running the install?
> 

I think the default (xp::install) does the right thing.  You don't
_have_ to call xp::install, (although Gcl needs the functions provided
by XP for conformance) and there is also an option to remove the
effects of installing.  Xpx is 'just' example code, it is certainly
not necessary for XP.  It provides an example of how to use the
pprinter to print (a subset of) Common Lisp as Pascal.

Regards,
Peter

Attachment: xp-test.txt
Description: Text document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]