On Tue 13 Feb 2024 at 08:35, Thorsten Jolitz <picolisp@software-lab.de> wrote: > But shouldn't hex 232300002424 print to something like ##^N^N$$ > instead of
no ^N could mean SO character with byte value 14 see the program ascii a NUL character would be displayed as ^@ > So the printed ASCII string (as char) carries all the information from the > hex string, and can be converted back to the exact same hex string? no, you are using wrong tool for the job as Alex said, a picolisp string cannot contain NUL byte > At least in some special cases when it's needed? arbitrary binary data is not a string parse the binary data properly -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
