ygrek has quit [Remote host closed the connection]
corecheckno has joined #picolisp
ygrek has joined #picolisp
corecheckno has quit [Remote host closed the connection]
aw- has quit [*.net *.split]
beneroth has quit [*.net *.split]
aw- has joined #picolisp
beneroth has joined #picolisp
ygrek has quit [Remote host closed the connection]
rob_w has joined #picolisp
geri has joined #picolisp
<geri>
hey-hey
<abu[7]>
o/
<geri>
silly question - IO system was originally basically a bunch of wrappers over C's stuff right? :D
<abu[7]>
T
<abu[7]>
stdio
<geri>
alriiight
<geri>
i was confused how to implement io system for my interpreter
<geri>
and im yet again realizing how nice io system in picolisp is
<geri>
explicit opening and closing of streams is ouch
<abu[7]>
Hmm, also back in C it was direct syscalls
<abu[7]>
read(), write()
<geri>
always or for some particular functions?
<geri>
s/functions/builtins
<abu[7]>
Mostly iirc
<geri>
interesting
<abu[7]>
only miniPicoLisp used stdio exclusively
<abu[7]>
pil32 and pil64 pehaps only fprintf on stderr for some error messages
<abu[7]>
btw, pil21 is the same as pil32/pil64 in this regard
<geri>
neat, neat
<geri>
i guess part of the reason why picolisp is posix-only
<abu[7]>
Not so much. File I/O is possible everywhere
<abu[7]>
It is pipes, fork etc
<abu[7]>
also TTY
<geri>
file descriptors maybe
<abu[7]>
not really
<geri>
could assign your own integers to opened file streams
<abu[7]>
T
<abu[7]>
eg. ErsatzLisp was no Posix
<abu[7]>
files are no problem
<abu[7]>
It is processes and TTY mainly
<geri>
test
<geri>
is it as cross-platform as java itself?
<abu[7]>
Ersatz?
<geri>
yes
<abu[7]>
It is 100% Java
<abu[7]>
not really usable. Just a toy project :)
<geri>
:(
<geri>
i thought its a real dialect and stuff
<abu[7]>
The lang is just PicoLisp, but all Posix features removed
<abu[7]>
same in miniPicoLisp
<geri>
but io is still in place and fine
<geri>
pretty interesting stuff
<abu[7]>
no piped I/O though
<geri>
could maybe implement posix features with a ton of abstraction but lost performance and not a fact it'll be implementable in other OS'es and such
<abu[7]>
stdio is enough then
<abu[7]>
Check out miniPicoLisp
<geri>
seen it but hadn't written anything in it
<geri>
looks interesting, i like my minimalism
<abu[7]>
I've also never really used it
<geri>
thats so sad
<abu[7]>
Some people put it on embedded hardware
<geri>
iirc it uses even less resources than normal picolisp no?
<beneroth>
fixed version: 3.4.0 or above, check with: rsync --version
<aw->
beneroth: thanks! bitsavers should be notified
<beneroth>
aw-, you're welcome! yes, public servers are specifically a concern. For most other setups it's probably not extremely urgent but updating asap is surely a good idea
<beneroth>
not sure if OS repos (debian et al) already have updated packages
<beneroth>
the BSDs listed as "not affected" are only not affected because they don't have rsync in the default install. "not affected" in those cases doesn't mean the port repo is necessarily updated.
<aw->
yikes
<aw->
that seems irresponsible
<beneroth>
potentially misleading - then again there must be a line/limit to responsibility somewhere, and the BSDs usually state clearly that their claims are only about the default installation.. but yes.
<beneroth>
I'm not sure who operates the repos, but in my book the repo operators surely have a responsibility.