mmmattyx has quit [Quit: Connection closed for inactivity]
casaca has quit [Remote host closed the connection]
casaca has joined #picolisp
orivej has joined #picolisp
orivej has quit [Ping timeout: 265 seconds]
orivej has joined #picolisp
<tankf33der>
How to detect i run on pil21?
<Regenaxer>
(>= (car (version)) 21) ?
<tankf33der>
Ok
<tankf33der>
But someday you will fix something on pil64 and it became 21 too
<Regenaxer>
I plan never to touch pil64 again ;)
<Regenaxer>
Another difference is *CPU -> "aarch64" on pil21 but "arm64" on pil64
<Regenaxer>
Not reliable
<Regenaxer>
Another check: (bool llvm)
<Regenaxer>
(if llvm (pil21) (pil64))
<Regenaxer>
But this works only with pil +
<Regenaxer>
Not a good idea
<tankf33der>
I see
<tankf33der>
ok
<tankf33der>
i will remove pil64 everywhere, lets see how long i will survive.
orivej has quit [Ping timeout: 256 seconds]
<Regenaxer>
yeah :)
<Regenaxer>
Same here
orivej has joined #picolisp
orivej has quit [Ping timeout: 264 seconds]
logand has joined #picolisp
orivej has joined #picolisp
* beneroth
still loves pil64 <3 <3
<Regenaxer>
good ;)
<aw->
beneroth: ;)
<aw->
i also got rid of pil64 everywhere
<aw->
a few months ago, no noticeable issues
<Regenaxer>
Good to know, any bug result welcome
<beneroth>
nice to know, thanks aw- :D
<beneroth>
main reason I haven't done much with pil21 yet has nothing to do with pil21, just still too much work, so I stay with an (slightly older) version
<beneroth>
secondly my C++ past ("optimize for runtime not devtime" - yes I learned it is wrong, that is how I came here ;-)) still tries to nag me, so I'd like to bench eventually pil21/pil64 for performance/energy consumption
<Regenaxer>
I have also some apps still running on pil64, there was no need to touch them yet
<beneroth>
maybe there is a difference if you run the server - but probably not worth it
<beneroth>
and energy consumption doesn't matter, unfortunately
<beneroth>
Regenaxer, yeah that is the reason I'm not so up to date :)
<Regenaxer>
best strategy
<Regenaxer>
Locally I debug all on pil21 whenever needed
<beneroth>
you said something about there being differences how pipe work between pil21 vs pil64 ?
<beneroth>
I didn't understand that.. because the pipes are the same unix pipes, no? or you give them some other flags now internally, so they behave differently?
<Regenaxer>
Hmm, I don't remember, but if so it is fixed
<beneroth>
no bug afaik, just the fact that opening many pipes in short time might result in having to many pipes/fd open at same time, because they're not closed quickly enough (independent on lisp level code)
<Regenaxer>
the pipes are Unix, yes
<Regenaxer>
but the setup of the processes is done by pil
<beneroth>
e.g. (pipe) and the implicit pipes in (in 'lst) calls
<Regenaxer>
same in 64 and 21
mmmattyx has joined #picolisp
Seteeri has joined #picolisp
logand has quit [Ping timeout: 256 seconds]
orivej has quit [Ping timeout: 265 seconds]
orivej has joined #picolisp
logand has joined #picolisp
mmmattyx has quit [Quit: Connection closed for inactivity]