This development release adds divert sockets/ports to net-listen (UNIX only) and adds other miscellaneous features and enhancements.
Files and CHANGES notes: http://www.newlisp.org/downloads/development
newLISP development release v.10.2.18
Re: newLISP development release v.10.2.18
Thank you for great works, Lutz.
I finished translating manual of v.10.2.18 into Japanese.
http://cid-23a9a25e1aec3626.skydrive.li ... -10218.zip
Also, current version rev-22.
http://cid-23a9a25e1aec3626.skydrive.li ... -10208.zip
By the Way, according to the manual,
Is it another reason ? or specification ?
Also, current version is same in UTF-8–enabled newLISP.
Maybe, it is no problem, because explode could not use for binary content in UTF-8–enabled newLISP.
I finished translating manual of v.10.2.18 into Japanese.
http://cid-23a9a25e1aec3626.skydrive.li ... -10218.zip
Also, current version rev-22.
http://cid-23a9a25e1aec3626.skydrive.li ... -10208.zip
By the Way, according to the manual,
And,explode also works on binary content:
At example,When called in UTF-8–enabled versions of newLISP, explode will work on character boundaries rather than byte boundaries.
Code: Select all
newLISP v.10.2.18 on Win32 IPv4/6 UTF-8, execute 'newlisp -h' for more info.
> (explode "\000\001\002\003")
("")
>
Also, current version is same in UTF-8–enabled newLISP.
Maybe, it is no problem, because explode could not use for binary content in UTF-8–enabled newLISP.
Re: newLISP development release v.10.2.18
Thanks Johu, the manual description was wrong, only non-UTF8 newLISP can split binary contents (containing 0 characters). On UTF8 versions processing stops at binary 0's. The 'unpack' function can be used for UTF8 versions to split into bytes:
This code would works on both versions of newLISP.
I have changed the the description of 'explode' in the 10.2.18 manual:
http://www.newlisp.org/downloads/develo ... ml#explode
ps: Your translations are online.
Code: Select all
set 'str "\001\002\003\004") ;=> "\001\002\003\004"
(unpack (dup "c" (length str)) str) ;=> (1 2 3 4)
(unpack (dup "s" (length str)) str) ;=> ("\001" "\002" "\003" "\004")
I have changed the the description of 'explode' in the 10.2.18 manual:
http://www.newlisp.org/downloads/develo ... ml#explode
ps: Your translations are online.
Re: newLISP development release v.10.2.18
Thank you, Lutz.
I am glad to see that binary contents are operated in UTF8-enabled newLISP.
Regards,
I am glad to see that binary contents are operated in UTF8-enabled newLISP.
Regards,