Hi Vijay, > I compiled the full PicoLisp natively on Plan9, without using GCC. I > am planning to replace the POSIX/Sockets functions with Plan9's > simple, 'file io' style interface for networking, cpu sharing etc. > Plan9 specific features like channels, graphics and threads will be > added so that Pico can be used as a full 'systems' language for that > OS.
Wow, great! :) > As there will be so many changes and new low-level functions, do I > have to call this port "SomeLisp derived from PicoLisp"? You are completely free to choose any name you like. For me, staying with "PicoLisp" would be all right, as the language itself stays the same. If Plan9 had supported dynamic linking, you could even keep the core language, and put channels, graphics etc. into a separate lib. But as I understand from the previous explanations, this is not an option. However, please be aware the threads (in the sense of pre-emptive threads - IIRC, we've discussed that also in this mailing list) will principally not be possible with the PicoLisp VM. Cheers, - Alex -- UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe
