Unsubscribe

Good bye Rand Dow :-( You are now unsubscribed -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Announce: PicoLisp in Hardware (PilMCU)

This has made it to #4 on Hacker News (https://news.ycombinator.com). That’s pretty impressive, Alex! — Rand-- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe

Re: Solved: Tell mechanism issue (perhaps OT)

I believe that modern Linux and FreeBSD implementations use 32 bit ints for the pid_t. There will never be that many processes on a 32 bit OS, but since they just go forward until they wrap, getting a pid bigger than 16 bits is probably even to be expected. On Aug 6, 2014, at 11:43 AM,

Re: Regarding the implementations of PicoLisp

On May 14, 2014, at 7:42 AM, Jakob Eriksson ja...@aurorasystems.eu wrote: There is also the larger picture. Which is best, having unencrypted communications and knowing it, or having encrypted communications, but unaware of the gaping in holes in security? Or even better, encrypting your data

Re: Regarding the implementations of PicoLisp

Hi Tiffany, This could be quite interesting — indeed in “Salem”. Nothing to really view — I can do a “drive by”. Could you check if there is any thing going on, like “pending”, etc.? 4898 Riverdale Rd S, Salem, OR Randy On May 9, 2014, at 7:07 AM, Rick Lyman lyman.r...@gmail.com wrote:

Re: Patch: Exit status for call

This sounds like the right solution to me, Alex. Using @@ would be analogous to the C interface to system calls storing the error code in 'errno'. Rand On Feb 24, 2014, at 6:22 PM, Alexander Burger a...@software-lab.de wrote: Hi Konstantin, Right, the exit status is not stored anywhere

Re: Are PicoLisp's coroutine stacks legal?

implement green threads, coroutines or continuations? Since that is read/write memory, the system won't purge it. It might be paged out (to swap), but would be transparently paged back in if/when used again. I'd never expect an OS to know that a region of memory is a stack. Rand

Re: Are PicoLisp's coroutine stacks legal?

chance of using a lot of stack. Rand On Tue, May 21, 2013 at 6:55 PM, Alexander Burger a...@software-lab.dewrote: Yep. That's the trade-off. As soon as you use a coroutine in PicoLisp, you have to be conscious about your stack. For a program that has no coroutine active when a lot of stack

Re: Are PicoLisp's coroutine stacks legal?

switch occurs, the switched to routine could find it's stack corrupted. And certainly operating system events could overwrite things deeper on the stack during a context switch. Rand On Mon, May 20, 2013 at 6:43 PM, Alexander Burger a...@software-lab.dewrote: Hi all, since nearly three years

Re: Are PicoLisp's coroutine stacks legal?

Hi Alex, On May 21, 2013, at 7:02 AM, Alexander Burger a...@software-lab.de wrote: On Tue, May 21, 2013 at 05:56:52AM +0200, Rand Dow wrote: Each co-routine should have it's own separate stack. Best practices with stack management today have a sufficiently large stack that grows

Re: In Detail: Native C Calls

Alex, That looks great! I'm very impressed with native and now he doc! Cheers! Rand On May 9, 2012, at 3:33 PM, Alexander Burger a...@software-lab.de wrote: Hi all, at last, I have found the time to write an in-detail description of the 'native' function: http://software-lab.de/doc

subscribe

Hello :-) You are now subscribed subscribe = -- UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: Installation on PowerPC Mac running OS X 10.411

Kyle, The GCC compiler is contained in a package called "xcode". Cheers, - Rand = -- UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

unsubscribe

Good bye [EMAIL PROTECTED] :-( You are now unsubscribed move address -- Randall Dow Pfarrer-Faustner-Weg 1, D-82008 Unterhaching +49-176-24129991 -- UNSUBSCRIBE: mailto:[EMAIL PROTECTED]

picoWiki

Hi all, I think I have said this before, but I will repeat it. In my experience, a Wiki is only truly successful if there are very clear rules, styles, and usually someone with a heavy hand to enforce that. I think that the original author of picolisp may be concerned that he gives up the

Re: Asyncronous IO

Henrik, take a look at http://docs.python.org/library/asyncore.html There is even a few samples. I have used this extensively, reimplemented it directly in C a time or two. I think it would be relatively simple to implement using 'task' and '*Run'. Rand Henrik Sarvell wrote: Sounds

Re: Asyncronous IO

Labs these days? They do still exist. Rand -- UNSUBSCRIBE: mailto:[EMAIL PROTECTED]

Re: Asyncronous IO

Henrik Sarvell wrote: Thanks Randall for that! So where do we start, where do I start, am I needed? I just don't have time now to really look into it. :-( Is the best way to simply review the Twisted source and reimplementing in Pico, keeping the OODB in mind all the time maybe? I would

Re: 'date' and 'time'

midnight rollover. (setq LDate (date) LTime (time T)) will give you the local date and time with no midnight rollover. Rand Randall Dow Witneystrasse 7, D-82008 Unterhaching, Germany phone: +49-89-12417690 mobile: +49-176-24129991 Andrei Ivushkin wrote: Guys, please clarify: (date) When