Re: PicoLisp SSL Problem

Look at this: http://forums.mozillazine.org/viewtopic.php?f=38t=2416901 -- Rand On Feb 15, 2012, at 11:52 AM, Henrik Sarvell wrote: Yes, if FF blocks the result before Tamper gets to access it then what I said above is not correct, that is the big caveat. On Wed, Feb 15, 2012 at 5:43

Re: PicoLisp is DEAD (Was: PicoLisp and its (lack of) libraries)

I have to agree with Alex here. This language has its place and is very useful in that place. I am currently doing embedded in C, and have no choice about what to use. But I have to say, I in very much in favor of the succinctness of PicoLisp and its ability to link with any library. If someone,

Re: UB-Tree support

Hi Alex, I added an account recently apobits to Twitter - this is for an idea I am working on. Since it has to be portable to Mac, Windows, Android and iPhone, I have to do it in C, not picolisp :-( BTW, the verb form is twittered or better tweeted. A twitter is the sound a bird makes, and

Re: Problems with +Blob

Hi Henrik, I just went and read that too - links per inode would include both directories or files or a mix of both. I checked the filesystem code for this, the ext3 inode is limited by a 16bit links_count. Under linux (UNIX) a directory simply contains a list of names and their inodes (a link) -

Re: First 64-bit release

Hi Alex, Thanks for the explanation. I haven't seriously programmed in assembly since 1986. However, the mental transitions that you mention are very familiar to me. I remember starting to write macros for everything and very soon it didn't matter that there were often unnecessary instructions

Re: Compiling on Mac

Hi Alex, From http://www.apple.com/macosx/ Coming September 2009 with every new Mac. Upgrade from Mac OS X Leopard f= or just $29. Yeah, it could be hoped that they also update the assembler. But there will likely be call interface updates and so on, and the 32 bit version will continue to

Re: Pico Bus error with OpenGL on Mac

Hi Alex, The *.s files don't assemble as expected: $ as -n x86-64.linux.base.s x86-64.linux.base.s:3:Unknown pseudo-op: .equiv x86-64.linux.base.s:3:Rest of line ignored. 1st junk character valued 72 (H). x86-64.linux.base.s:4:Unknown pseudo-op: .equiv x86-64.linux.base.s:4:Rest of line ignored.

Re: 'native' and errno or *Err

Hi Alex, I tried to compile the 64 bit version on my macbook yesterday - no joy. I think I have to create the /usr/bin/picolisp and /usr/lib/picolisp links to the 32 bit version and then create the .s files. I didn't get that far yet. Thanks for the 'errno' call. I'll try again this

Compiling on Mac (was: 'native' and errno or *Err)

Hi Alex, I don't have the specifics in my head, but it complains that it cannot find *darwin*.s files. And when I just try as linux.*.s I get a lot of error messages. I haven't looked deeper yet, but the as may be tuned somehow for Mac - it is GNU as, but . I'll take a closer look this

'native' and errno or *Err

Hi Alex, I am trying to use 'native', am getting only 'NIL' as the return value, where I would like to be getting a file descriptor number. How do I get the value of errno after my call? Cheers, - Rand -- UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: Deprecate 'begin'?

Hi Alex, none from me! Rand On Sat, Jul 11, 2009 at 12:17 PM, Alexander Burgera...@software-lab.de wrote: Hi all, has anybody ever used 'begin' (i.e. nested database transactions)? I'd rather doubt it. I used it just once, and only for a short time. This functionality cannot be

Re: The 'native' function (Was: First 64-bit release)

Hi Alex, This looks very cool! Yes, that is what I wished for at bmsc. Thanks! Rand On Tue, Jul 7, 2009 at 7:48 PM, Alexander Burgera...@software-lab.de wrote: now the 'native' C function call is working. It is in the testing release, and I think it looks quite nice! :-) -- UNSUBSCRIBE:

Re: Pico Bus error with OpenGL on Mac

Three things for me to try this evening... Rand On Wed, Jun 17, 2009 at 4:40 PM, Tomas Hlavaty t...@logand.com wrote: Hi Jon, Randall and Alex, this might not be related but still an idea. =C2=A0Have you tried to buil= d picolisp with gcc optimizations off? =C2=A0Recently, I had a problem

Re: Pico Bus error with OpenGL on Mac

Jon, Perhaps I can try it this week. I am interested in this. Alex, would you like to arrange a debugging session with me on a return trip through Munich? Rand On Tue, Jun 16, 2009 at 10:23 AM, Jon Kleiserjon.klei...@usit.uio.no wrote: I have now tested the OpenGL programs again, with the

Re: Pico Bus error with OpenGL on Mac

Hi Alex, I'll get everything installed, and let you know if I can reproduce the problem. Cheers, - Rand On Tue, Jun 16, 2009 at 11:20 AM, Alexander Burgera...@software-lab.de wrote: Alex, would you like to arrange a debugging session with me on a return trip through Munich? Good idea! I

Re: Pico Bus error with OpenGL on Mac

. Cheers, - Rand On Tue, Jun 16, 2009 at 11:51 AM, Randall Dow randall@gmail.com wrote: I'll get everything installed, and let you know if I can reproduce the problem. -- UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Re: 'call' function disables echoing input

Hi Alex, Do shells really? A simple case of the opposite: start vim, kill -9 from another shell, and you have to type stty sane. I think it is more up to the application to save and restore. Although, picolisp does bring surprises, whether you start with dbg.l and *Dbg on or not. But I think

Re: 'call' function disables echoing input

Hi Alex, So, something must still be wrong. I just never noticed it because I only called non-interactive processes (except 'vim'). But that is my point - vim goes to a lot of effort to handle the STOP and CONT signals and get the terminal handling right. I have created apps similar to vim -

Re: postscript utf8

Hi Tomas, I would presume that you are beginning to get close to the reason that one often encapsulates strings into an object. You need to know the display length of something to center it, and that means that you want to know the length of the string. Without an encapsulating object, you need

Re: parsing input

Hi Alex, Thanks, will try it, now going to pick up Francesca. - Rand On Sat, Apr 25, 2009 at 7:41 AM, Alexander Burger a...@software-lab.de wro= te: Hi Tomas, 01/02/2009 =C2=A0 30.00 =C2=A0 =C2=A0400.00 =C2=A0 =C2=A0t =C2=A0 =C2= =A0Randall Dow ... (use (@A @B @C @D @E) =C2=A0

Re: parsing input

Thanks all! (let L (mapcar pack (filter prog (split (line) ))) converts: 01/02/2009 30.00400.00tRandall Dow to (01/02/2009 30.00 400.00 t Randall Dow) which is just what I want. I could have left out the '(mapcar pack' and left it as a char list, which would still produce a more

parsing input

Hi Alex, I read a line, which looks something like: 01/02/2009 30.00400.00tRandall Dow in which the fields are separated by a varying number of spaces. That gets put into L, and then I delete the NILs that come from multiple spaces. Do you have a suggestion for a better way than

Re: database contest article

Hey, this is getting to be fun! Alex, thanks for stopping and having a beer! Till next time! Cheers! - Rand On Thu, Dec 4, 2008 at 6:56 PM, Alexander Burger [EMAIL PROTECTED]wrote: On Thu, Dec 04, 2008 at 05:06:39PM +, Tomas Hlavaty wrote: are we officially adopting blame culture? ;-)

unsubscribe

Good bye [EMAIL PROTECTED] :-( You are now unsubscribed moving address -- UNSUBSCRIBE: mailto:[EMAIL PROTECTED]

subscribe

--=_Part_49457_20659296.1224836490221 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hmm, that didn't work! -- Randall Dow +49-176-24129991 --=_Part_49457_20659296.1224836490221 Content-Type: text/html; charset=ISO-8859-1

subscribe

--=_Part_3856_17715030.1224838301864 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- Cheers! - Rand +49-176-24129991 home: +49-89-12417690 --=_Part_3856_17715030.1224838301864 Content-Type: text/html; charset=ISO-8859-1

How to best ...

. Thanks! Rand -- Randall Dow Witneystrasse 7, D-82008 Unterhaching, Germany phone: +49-89-12417690 mobile: +49-176-24129991 -- UNSUBSCRIBE: mailto:[EMAIL PROTECTED]