From ... From: Erik Naggum Subject: Re: strings and characters Date: 2000/03/18 Message-ID: <3162408282242844@naggum.no>#1/1 X-Deja-AN: 599330450 References: <3162184639382952@naggum.no> <3162300918453715@naggum.no> <3162358302244558@naggum.no> mail-copies-to: never Content-Type: text/plain; charset=us-ascii X-Complaints-To: newsmaster@eunet.no X-Trace: oslo-nntp.eunet.no 953419485 18849 195.0.192.66 (18 Mar 2000 22:44:45 GMT) Organization: Naggum Software; vox: +47 8800 8879; fax: +47 8800 8601; http://www.naggum.no User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.5 Mime-Version: 1.0 NNTP-Posting-Date: 18 Mar 2000 22:44:45 GMT Newsgroups: comp.lang.lisp * Tim Bradshaw | This doesn't work (unless I've misunderstood you) because I can't use | it for the string->unsigned-byte-array case, because the strings might | have big characters in them. sigh. so read (unsigned-byte 8), smash the type code so it's a string of non-big characters, and do _whatever_ you need to do with the string, then smash the type code and write (unsigned-byte 8) to whatever. | It looks to me like the outcome of all this is that there isn't a | portable CL way of ensuring what I need to be true is true, and that I | need to ask vendors for per-implementation answers, and meantime punt on | the issue until my code is more stable. Which are fine answers from my | point of view, in case anyone thinks I'm making the standard `lisp won't | let me do x' complaint. portable languages are for portable problems. conversely, non-portable problems may require non-portable solutions. I don't have a problem with that, but many seem to have. #:Erik