headers
András Simon | 1 Jun 2004 11:39
Picon

pprint-logical-block


(pprint-logical-block (nil nil) (terpri))

gives

Debugger invoked on condition of type TYPE-ERROR:

  The value #S(XP::XP-STRUCTURE [....]) is not of type character output stream.

Andras

-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
Permalink | Reply | 3 comments |
headers
András Simon | 1 Jun 2004 16:29
Picon

Re: pprint-logical-block

The funny thing is, this doesn't happen in the XP package:

XP(137): (pprint-logical-block (nil nil ) (write-char #\A))
A
NIL
XP(138):

Andras

On Tue, 1 Jun 2004, [X-UNKNOWN] András Simon wrote:

>
> (pprint-logical-block (nil nil) (terpri))
>
> gives
>
> Debugger invoked on condition of type TYPE-ERROR:
>
>   The value #S(XP::XP-STRUCTURE [....]) is not of type character output stream.
>
> Andras
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: Oracle 10g
> Get certified on the hottest thing ever to hit the market... Oracle 10g.
> Take an Oracle 10g class now, and we'll give you the exam FREE.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Peter Graves | 1 Jun 2004 21:24

Re: pprint-logical-block

On Tue, 1 Jun 2004 at 16:29:11 +0200, András Simon wrote:
> The funny thing is, this doesn't happen in the XP package:
>
> XP(137): (pprint-logical-block (nil nil ) (write-char #\A))
> A
> NIL
> XP(138):
>
> Andras
>
> On Tue, 1 Jun 2004, András Simon wrote:
>
> >
> > (pprint-logical-block (nil nil) (terpri))
> >
> > gives
> >
> > Debugger invoked on condition of type TYPE-ERROR:
> >
> >   The value #S(XP::XP-STRUCTURE [....]) is not of type character output stream.
> >
> > Andras

Currently ABCL uses the original XP package for pretty printing ("This
is the November, 26 1991 version of Richard C. Waters' XP pretty
printer"), hacked up just enough so that on a good day it barely works
at all.

This isn't really meant to be a permanent solution. Before undertaking
any major work in this area, however, I'd like to wait until there are
(Continue reading)

Permalink | Reply | 1 comment |
headers
András Simon | 2 Jun 2004 00:54
Picon

Re: pprint-logical-block


On Tue, 1 Jun 2004, Peter Graves wrote:

> Currently ABCL uses the original XP package for pretty printing ("This
> is the November, 26 1991 version of Richard C. Waters' XP pretty
> printer"), hacked up just enough so that on a good day it barely works
> at all.
>
> This isn't really meant to be a permanent solution. Before undertaking
> any major work in this area, however, I'd like to wait until there are
> tests for pretty printing in the ANSI test suite. Without tests, it's
> hard to know whether the net effect of a given change is positive or
> negative, even if the change appears to fix some particular problem.
> And I still haven't decided whether the right long-term approach
> involves more hacking on the existing XP code or a complete, from-the-
> ground-up rewrite.

I see. I thought XP was meant to be a permanent solution. (Actually,
it usually works pretty well for me.)

> I'll try to take a look at the specific issue with PPRINT-LOGICAL-BLOCK

Please consider it a very low priority thing! It's not like this is a
major stumbling block for me.

Andras

-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
(Continue reading)

Permalink | Reply | 0 comments |
headers
Simon András | 7 Jun 2004 11:40
Picon

slime

I have slime working with abcl. It's not perfect, but already usable.

If anyone is interested (either in using it or in working on it) ,
I'll try to clean it up a bit (get rid of debugging code and possible
local dependencies); otherwise I'll wait at least until c-l.net is
back. Though even then, incorporating abcl support in the "official"
slime may take a while, because (a) I had to change swank.lisp a
little (to use xp::write-char and xp::terpri at one point) and (b) one
has to REQUIRE a few abcl modules before slime can be loaded.

Andras

-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
Permalink | Reply | 6 comments |
headers
Peter Graves | 7 Jun 2004 16:54

Re: slime

On Mon, 7 Jun 2004 at 11:40:37 +0200, Simon_András wrote:
> I have slime working with abcl. It's not perfect, but already usable.

That's great news!

> If anyone is interested (either in using it or in working on it) ,
> I'll try to clean it up a bit (get rid of debugging code and possible
> local dependencies); otherwise I'll wait at least until c-l.net is
> back. Though even then, incorporating abcl support in the "official"
> slime may take a while, because (a) I had to change swank.lisp a
> little (to use xp::write-char and xp::terpri at one point) and (b) one
> has to REQUIRE a few abcl modules before slime can be loaded.

(a) I think I've fixed things in CVS so that this is no longer
necessary.

I'm in the process of getting rid of the shadowed-symbol-weirdness in
pprint.lisp, and although I'm not completely finished with that
project, I've done WRITE-CHAR and TERPRI and that code is checked in.

(b) Which modules need to be REQUIRE'd? Autoload doesn't work for this,
for some reason? (What exactly does slime want?)

-Peter

-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
(Continue reading)

Permalink | Reply | 5 comments |
headers
Simon András | 7 Jun 2004 17:43
Picon

Re: slime


On Mon, 7 Jun 2004, Peter Graves wrote:

> > If anyone is interested (either in using it or in working on it) ,
> > I'll try to clean it up a bit (get rid of debugging code and possible
> > local dependencies); otherwise I'll wait at least until c-l.net is
> > back. Though even then, incorporating abcl support in the "official"
> > slime may take a while, because (a) I had to change swank.lisp a
> > little (to use xp::write-char and xp::terpri at one point) and (b) one
> > has to REQUIRE a few abcl modules before slime can be loaded.
>
> (a) I think I've fixed things in CVS so that this is no longer
> necessary.

Great, thanks!

>
> I'm in the process of getting rid of the shadowed-symbol-weirdness in
> pprint.lisp, and although I'm not completely finished with that
> project, I've done WRITE-CHAR and TERPRI and that code is checked in.

Actually, WRITE-CHAR is enough I think for slime (I know I mentioned
TERPRI but that was a mistake).

>
> (b) Which modules need to be REQUIRE'd? Autoload doesn't work for this,
> for some reason? (What exactly does slime want?)

search, gray-streams, pprint, and format. Now I REQUIRE these at the
top of swank-abcl.lisp, so it's not a problem anymore. And now that
(Continue reading)

Permalink | Reply | 4 comments |
headers
Mike Beedle | 7 Jun 2004 18:27

RE: slime


Andras:

I am interested in making ABL work with slime as well.

Any chance you can share the snipplet of your .emacs file that loads
slime with ABL, and your swank-loader.lisp file?

I am sure I would make it work eventually, but I'd rather spend my 
cycles elsewhere,

- Mike

> -----Original Message-----
> From: armedbear-j-devel-admin <at> lists.sourceforge.net 
> [mailto:armedbear-j-devel-admin <at> lists.sourceforge.net] On 
> Behalf Of Simon András
> Sent: Monday, June 07, 2004 10:44 AM
> To: Peter Graves
> Cc: armedbear-j-devel <at> lists.sourceforge.net
> Subject: Re: [j-devel] slime
> 
> 
> 
> 
> On Mon, 7 Jun 2004, Peter Graves wrote:
> 
> > > If anyone is interested (either in using it or in working 
> on it) , 
> > > I'll try to clean it up a bit (get rid of debugging code and
(Continue reading)

Permalink | Reply | 2 comments |
headers
Simon András | 7 Jun 2004 18:40
Picon

Re: slime


On Mon, 7 Jun 2004, Simon András wrote:

> (On the other hand, since I updated abcl with your pprint-related
> fixes, slime crashes if the debugger is entered :-( I hope I'll find
> out why.)

OK, it was probably a pprint/gray-streams issue. Changing one PPRINT
to PRINT solved the problem (and since this is just for printing
frames, it doesn't make much difference).

This just shows that the gray-streams hack I added a few days ago is
nowhere near well-tested (actually I'm quite surprised that it's
usually good enough for slime). Does anyone know of a test suite for
gray-streams?

Andras

-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
Permalink | Reply | 0 comments |
headers
Simon András | 7 Jun 2004 19:19
Picon

RE: slime


On Mon, 7 Jun 2004, Mike Beedle wrote:

>
> Andras:
>
> I am interested in making ABL work with slime as well.
>
> Any chance you can share the snipplet of your .emacs file that loads
> slime with ABL, and your swank-loader.lisp file?

http://www.math.bme.hu/~asimon/slime-abcl.tgz contains all the
necessary ingredients (apart from slime itself):

dot-emacs
swank-loader.lisp
swank-abcl.lisp

[Note that swank-abcl.lisp is very much a work in progress. I haven't
tidied it up at all.]

You should untar it (after making a backup copy of your
swank-loader.lisp!) in the directory you keep slime in, and paste the
contents of the dot-emacs file (with pathnames changed to suit your
setup) in your .emacs.

Make sure you (a) have a very recent cvs version of abcl (you may need
to recompile the whole thing if you haven't updated the sources for
some time) (b) don't have fancy things in your ~/.swank.lisp; in
particular, changing the communication style (which is :SPAWN for
(Continue reading)

Permalink | Reply | 1 comment |

Gmane