Re: (native) wrapper around zlib
Hi Laurent, > It took the error message I got when I worked on the uncompress > function to realize that, indeed, InBuf should be a byte list, and > not a string... (this is binary data, and there are null bytes, and > a (pack (mapcar 'char TheList)) removes said bytes...) > Looking at the "Memory Management" section at > http://software-lab.de/doc/native.html, I am considering using > malloc (I will have many calls) but for what I have in mind, I would > need to be able to set and get the value of a malloc-ed variable > outside of a native call. > Is it possible? Yes. This should be possible with 'struct'. Cheers, - Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: (native) wrapper around zlib
Le 23/08/2012 08:57, Alexander Burger a écrit : Hi Laurent, It took the error message I got when I worked on the uncompress function to realize that, indeed, InBuf should be a byte list, and not a string... (this is binary data, and there are null bytes, and a (pack (mapcar 'char TheList)) removes said bytes...) Looking at the "Memory Management" section at http://software-lab.de/doc/native.html, I am considering using malloc (I will have many calls) but for what I have in mind, I would need to be able to set and get the value of a malloc-ed variable outside of a native call. Is it possible? Yes. This should be possible with 'struct'. Thanks! It works perfectly! Regards, -- Laurent ARTAUD (laurent.art...@free.fr) -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Almost 2000 pages of PicoLisp
Hi List, I just published (mainly as an editor) two free PicoLisp books in pdf format: ,--- | PicoLisp Works | http://www.scribd.com/doc/103732688/PicoLisp-Works | https://github.com/tj64/picolisp-works `--- , | PicoLisp by Example | http://www.scribd.com/doc/103733857/PicoLisp-by-Example | https://github.com/tj64/picolisp-by-example ` Have fun! PS I consider these free books community project now, so you are very welcome to help fixing the inevitable bugs and errors (its impossible to review 2000 pages). Just report anything wrong you notice here in the mailing list, or even better, clone the gitrepos, make a private branch, fix any mistakes you encounter, and send me a patch or pull request. -- cheers, Thorsten -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe