From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!skynet.be!skynet.be!ossa.telenet-ops.be!nmaster.kpnqwest.net!nreader1.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Back to character set implementation thinking References: <87ofhczdat.fsf_-_@becket.becket.net> <878z8cv4jw.fsf@becket.becket.net> Mail-Copies-To: never From: Erik Naggum Message-ID: <3226402339496495@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 21 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 Mar 2002 14:52:04 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader1.kpnqwest.net 1017413524 193.71.199.50 (Fri, 29 Mar 2002 15:52:04 MET) NNTP-Posting-Date: Fri, 29 Mar 2002 15:52:04 MET Xref: archiver1.google.com comp.lang.lisp:30523 * Brian Spilsbury | I think you need to differentiate between mutable and immutable | strings. I have suggested that strings need to be separated into two mor basic types: a stream which you read one element at a time, and a vector which provides random access. The former maps directly to files and is suitable for parsing and formatting, while a vector of characters is more useful for repeated access to the same characters. We have the system class string-stream today, which offers stream access to a string, but I think we need a subclass of string like stream-string, which may contain such things as the octets from another stream such as directly from an input file, and be processed sequentially, and therefore should also be able to use stateful encodings such that reading through them with the string-stream functions would maintain that state. /// -- In a fight against something, the fight has value, victory has none. In a fight for something, the fight is a loss, victory merely relief.