Hi,
I think Picowiki could use a title index. As somthing that is
automatically generated
regs
Konrad.
2008/10/13 Tomas Hlavaty <[EMAIL PROTECTED]>:
>> I will have to implement some picoWiki markup for html anchor for
>> this.
>
> Anchors is a bad idea actually. It does not go well with the
Hi Alex,
maybe it could become part of lib/xml.l? I would use it as it looks
more convenient than building list for 'xml' function in some cases.
Thanks,
Tomas
--
UNSUBSCRIBE: mailto:[EMAIL PROTECTED]
Hi Konrad,
> would you be able to tell me what all the arguments to the functions
> in nb.l actually are. I mean what are they used for not just data
> type, as I can't say i fully follow it beyound that the first argument
> to rdx is a list beign used as a buffer.
I put the description into pico
Hi all,
>> 1) Does the Interpretor do any kind of tail call optimisation, I
>
> No, not at all.
>
> As far as I can see, this is not easy to implement in an efficient way.
> The interpreter would have to detect tail recursion at runtime, which
> takes much more than time than simply executing the
Hi Thomas,
Now that I can run your async reading and writing code.
would you be able to tell me what all the arguments to the functions
in nb.l actually are. I mean what are they used for not just data
type, as I can't say i fully follow it beyound that the first argument
to rdx is a list beign u
THe interesting thing will be handling C structs. As almost every
interesting C API makes heavy use of them.
My wish list would be to be able to create them from inside pico and
use them just like a native object. IE pass them arround as the values
of symbols and use 'get' and
'put' to read and wr
On Mon, Oct 20, 2008 at 11:26:00PM +0700, Henrik Sarvell wrote:
> Simply manually navigating to http://localhost:8080/@desktop after
> this displays all the correct results. It seems I can not set the
> cookie and simply retrieve its contents through the use of *Cookies in
> the same request?
The
On Mon, Oct 20, 2008 at 04:21:31PM +0100, Tomas Hlavaty wrote:
> That's nice. It could even be:
>
> (de Prg
>(prin "<" (pop 'Prg))
>(while (atom (car Prg))
> (prin " " (pop 'Prg) "=\"" (eval (pop 'Prg) 1) "\"") )
>(prin ">")
>(run Prg) # the text, or other elements
>
Since redirect won't set the cookie I tried a workaround:
(de signin ()
(app)
(action
(html
..
(gui '(+Button) "Login"
'(if (chkLogin (val> (: home uname)) (val> (: home pwd)))
(redirect (pack *Domain "@desktop?+" @))
(err "Could not login.")))
..
This correctly routes
> How about the following?
>
>(de Prg
> (prin " (while (atom (car Prg))
> (prin " " (pop 'Prg) "=\"" (eval (pop 'Prg) 1) "\"") )
> (prin ">")
> (run Prg) # the text, or other elements
> (prinl "") )
>
> Then you could write
>
>: ( id 123 dx (+
Hi Jon,
> then the calls would very often have a lot of NIL arguments, which looks
> rather ugly. Should I switch to property lists? Any suggestions?
How about the following?
(de Prg
(prin "")
(run Prg) # the text, or other elements
(prinl "") )
Then you could write
Hi,
I've started some work on doing SVG graphics from Pico Lisp, and I've
written a few functions that produce SVG elements. I try to do this
more or less in the same way the HTML elements are done in
lib/xhtml.l. Some SVG elements have just a small number of
attributes, but others, like 'tex
12 matches
Mail list logo