• various fixes for UTF-8 handling in different functions, some affected the newLISP-tk frontend
• a new sqlite3.lsp handles FLOATs BLOBs and senses the library location depending on platform
For files and detailed change notes see http://newlisp.org/downloads/development/
Lutz
development version newLISP v. 8.5.5
Hi Lutz,
8.5.5 ->
'net-connect' and 'net-select' did not accept/convert floats for portnumbers/sockets
I dont understand? there are no float portnumbers/sockets,
according to the standard this is limited to 0 - 65534.
Or is it ment for conversion between i.e. Java/C++ and newlisp?
Regards, Norman
8.5.5 ->
'net-connect' and 'net-select' did not accept/convert floats for portnumbers/sockets
I dont understand? there are no float portnumbers/sockets,
according to the standard this is limited to 0 - 65534.
Or is it ment for conversion between i.e. Java/C++ and newlisp?
Regards, Norman
-- (define? (Cornflakes))
yes, but sometimes you may have something like this:
(dotimes (port N) (push (net-connect hostname port) connections))
in this case 'port' will be a float, becaused loop variables are floats even if if the frcational part is zero, because internally 'for', 'dotimes' and 'sequence' are all handled byn the same subroutine. There are many functions in newLISP which use integers, but do automatically convert from float, i.e. all indices etc.. And there are many functions taking floats but automatically converting from integer if required, i.e. all trigonometric functions.
Lutz
(dotimes (port N) (push (net-connect hostname port) connections))
in this case 'port' will be a float, becaused loop variables are floats even if if the frcational part is zero, because internally 'for', 'dotimes' and 'sequence' are all handled byn the same subroutine. There are many functions in newLISP which use integers, but do automatically convert from float, i.e. all indices etc.. And there are many functions taking floats but automatically converting from integer if required, i.e. all trigonometric functions.
Lutz