This is the mail archive of the kawa@sources.redhat.com mailing list for the Kawa project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: readtable support added to Kawa


Jocelyn Paine wrote:
Should updating the result of (current-readtable) alter the behaviour of
reading on the current port?
Yes.

The problem appears to be that there are *two* readtables:
ReadTable.current and ScmRead.scmReadTable.  I don't remember
exactly why I did this, though it is tied in with the fact that
the "current readtable" is poorly specified, and that it might
be cleaner to say "readtable associated with the current input
port".  However, that way of doing it is difficult to make
compatible with Common Lisp.

The attached patch is at least beter than the current
situation, until I can think about it some more.
--
	--Per Bothner
per@bothner.com   http://www.bothner.com/per/
Index: ScmRead.java
===================================================================
RCS file: /cvs/kawa/kawa/gnu/kawa/lispexpr/ScmRead.java,v
retrieving revision 1.11
diff -u -r1.11 ScmRead.java
--- ScmRead.java	24 Jan 2002 00:01:55 -0000	1.11
+++ ScmRead.java	22 Jan 2003 19:07:17 -0000
@@ -19,17 +19,9 @@
     //initialColonIsKeyword = false;
   }
   
-  protected ReadTable getReadTable () { return scmReadTable; }
-
   public static Object readObject(InPort port)
       throws java.io.IOException, SyntaxException
   {
     return (new ScmRead(port)).readObject();
-  }
-
-  public static ReadTable scmReadTable;
-  static
-  {
-    scmReadTable = ReadTable.getInitial();
   }
 }

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]