Re: [clisp-list] Doing everything with bytes instead of chars

[<don...@is...>]

- I didn't think that declare optimize had any effect in clisp.
  http://clisp.podval.org/impnotes/declarations.html
  lists a very few effects:
  (OPTIMIZE (SAFETY 3))  function calls are never eliminated 
  SPACE >= 2 documentation string is discarded 
  SPACE >= 3 the original lambda list is also discarded
  If there are any others I think they should be listed there.

- I concluded long ago that what I normally want just can't be done:
  read every 8bit byte as a distinct character.
  The problem is not the charsets and encodings but newline handling.
  The best solution I have found is to read bytes and store their 
  code-char's into the strings your program uses.

- For things like http or mail servers it's generally better to use
  strings internally than byte vectors.  For general network traffic
  monitoring I like bytes better.

Although I don't know enough about your specific needs to be sure,
I generally think the approach being discussed of implementing a lot
of stuff in a new package is going to be counterproductive.

Append differs from concatenate in that the last list argument is
shared with the result, i.e., not copied.

  [13]> (string>= o o)
  256
CLHS:
 string>= string1 string2 &key start1 end1 start2 end2 => mismatch-index