<Regenaxer>
The HTML, SVG, PS and such functions have a rule
<Regenaxer>
Atoms are printed directly, lists are *evaluated*
<Regenaxer>
so it needs (prin (+ 1 1))
<Regenaxer>
I think we had this issue recently
<Regenaxer>
Was it in PilCon?
<tankf33der>
i dont know
<tankf33der>
i am just playing with tutorial
<Regenaxer>
good
<Regenaxer>
I did not put app.html into pil21
<Regenaxer>
It needs a lot of reworking I think
<beneroth>
Regenaxer, yeah we discussed "Atoms are printed directly, lists are *evaluated" during pilcon recently
<beneroth>
not the last one, one before or so
<Regenaxer>
Hi beneroth! Thanks for refreshing my memory! :)
<Regenaxer>
I think Olaf asked for that
<beneroth>
I think it's a good rule, also prevents accidental prints from any function calls
<beneroth>
return values or such, I mean
<Regenaxer>
right
<beneroth>
is there a document describing all changes between pil64 and pil21? especially "breaking" changes like (arg) and (pil) ?
<Regenaxer>
and automatic printing of atoms makes the code more readble, as many parts are just constant strings or numbers
<beneroth>
T
<Regenaxer>
yes, there is doc/diff
<beneroth>
oh okay
<beneroth>
the rolling release is still pil64? or you switched it to pil21 too?
<Regenaxer>
and the parts in doc/ref?.html should be updated
<beneroth>
ok
<Regenaxer>
Not switched yet
<beneroth>
kk
<Regenaxer>
More testing
<Regenaxer>
Then I ask also Kanru to change in Debian
<beneroth>
I will stay on pil64 a bit longer. Also I'm still in a big project. Ones that calms down I will switch my development environment to pil21 I think
<beneroth>
good :)
<Regenaxer>
On production servers I also did not switch yet
<Regenaxer>
only local development and testing
<beneroth>
I'm also considering to keep using pil21 in the long term, if feasible, for servers I control (for the performance benefit, if there is one - I should measure)
<Regenaxer>
good
<beneroth>
could be worth it for horizontal scaling (many picolisp instances)
<Regenaxer>
T
<beneroth>
but yeah, needs to be actually benchmarked
<beneroth>
oh I wanted to say pil64 in the last sentence xD
<beneroth>
anyway xD
<Regenaxer>
:)
<beneroth>
db format didn't change, I got that right,correct?
<Regenaxer>
yes
<Regenaxer>
interchangeable
<beneroth>
wunderbar.
<beneroth>
yeah!
<Regenaxer>
:)
aw- has quit [Quit: Leaving.]
aw- has joined #picolisp
<tankf33der>
my test suite still running under gc+, third week soon.
<beneroth>
impressive, tankf33der :)
<Regenaxer>
wow
mtsd has quit [Quit: Leaving]
rob_w has quit [Quit: Leaving]
dexen has joined #picolisp
LamBaah has joined #picolisp
LamBaah has quit [Remote host closed the connection]
<Regenaxer>
tankf33der, are you sure it does not hang?
<tankf33der>
yes, i see progress
<Regenaxer>
good
<dexen>
i've tried using the native call function today and was blown away with how neatly it's designed
<Regenaxer>
Glad to hear :)
<dexen>
now i'm stuck - how do i allocate buffer & pass a pointer to it to readlink(const char *pathname, char *buf, size_t bufsiz); ?
<Regenaxer>
There are 2 (in pil21 three) ways
<Regenaxer>
But in this case the easiest is to let 'native' do it directly
<Regenaxer>
(Buf (256))
<Regenaxer>
to get the value as bytes, '(Buf (16 B . 256))