Re: Where is term.l loaded?
Hi Thorsten, where term.l is loaded - where does this happen? ... I see, its not an essential part of the system. Thanks. Exactly. The line editor was kept simple (and in vi-mode) to avoid making the system terminal-dependent. Cheers, - Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
pil64emu testing features
Hi Alex, Using the latest ongoing picoLisp, I have briefly tested coroutines in pil64emu, and it works. I used the pythag code at http://picolisp.com/5000/!wiki?Coroutines Starting pil64emu with file argument, like ./bin/picolisp misc/fibo.l, still gives me a Segmentation fault. Are there other interesting 64-bit features I could try at the moment? /Jon -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: pil64emu testing features
Hi Jon, Using the latest ongoing picoLisp, I have briefly tested coroutines in pil64emu, and it works. I used the pythag code at Thanks for the testing! Perhaps you are a little bit too early. pil64emu isn't even announced here yet ;-) Starting pil64emu with file argument, like ./bin/picolisp misc/fibo.l, still gives me a Segmentation fault. What's definitely still missing is 'native' support. As misc/fibo.l also does some native stuff, perhaps this is the culprit? Are there other interesting 64-bit features I could try at the moment? I hope I can finish some basic 'native' support during this week. Let's postpone testing until then? Cheers, - Alex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
