Hi Wojtek,
> I'm wondering then... what if someone wanted to use PicoLisp to emit
> characters somewhere (say, to a listening process) and the case required
> one to send a null byte. Does this limitation extend to all attempts at
> representing the null byte or only in the file context?
As Andreas explained, you can use (wr 0) to output a null bybe.
In addition, to do arbitrary manipulations on I/O, you can use pipes. For
example, to read text in non-UTF8 format:
(in (list "/usr/bin/iconv" "-f" "ISO-8859-15" "-t" "UTF-8" File)
... )
and to write something:
(out (list "/usr/bin/iconv" "-o" File "-f" "UTF-8" "-t" "CP1252")
.... )
So there is no reason to bother PicoLisp itself with the mess of existing
character sets and file formats.
☺/ A!ex
--
UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
