From: Sam S. <sd...@gn...> - 2004-09-20 14:29:19
|
> * Bruno Haible <oe...@py...t> [2004-09-20 13:57:41 +0200]: > > Sam writes in the TODO: >> Many pretty-printer test failures. >> (Sam - but Bruno has to fix the risky-test in iofkts.tst first) > > Took a look at it, and found that I understand nothing about it. I think that the main issue is that the io.d PP has "flat" "TODO" lists of strings which prevents nested PP invocations, as exhibited by the aforementioned test. (note that individual objects are printed correctly, but not lists thereof). > I think, it will take me 2 or 3 months to work on the pretty-printer. > Probably I will start by writing the ANSI CL functionality in Lisp, > not C, (without *print-circle* handling), and then move selected parts > from Lisp to C. How it will integrate with the existing pretty > printer, I have no idea. I think that making the string lists nested will get you 90% of the way - the rest being bells and whistles. > This is not something I would like to hold up the MOP release for. So > my proposal is to schedule this for the 2.35 release, not 2.34. OK. PS. I would like to see Goffioul's embeddability patch in 2.35 too. -- Sam Steingold (http://www.podval.org/~sds) running w2k <http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/> <http://www.mideasttruth.com/> <http://www.honestreporting.com> If you try to fail, and succeed, which have you done? |