ChanServ changed the topic of #picolisp to: PicoLisp language | Channel Log: https://irclog.whitequark.org/picolisp/ | Check also http://www.picolisp.com for more information
orivej has quit [Ping timeout: 240 seconds]
casaca has quit [Remote host closed the connection]
casaca has joined #picolisp
orivej has joined #picolisp
orivej has quit [Ping timeout: 240 seconds]
rob_w has joined #picolisp
aw- has quit [Quit: Leaving.]
rob_w has quit [Remote host closed the connection]
rob_w has joined #picolisp
aw- has joined #picolisp
<beneroth> [security] OpenSSL DoS-vulnerability found. It's about certificate checking, so usually this will only affect clients unless client certificates are checked on server side. https://www.openssl.org/news/secadv/20201208.txt
Wiin has joined #picolisp
orivej has joined #picolisp
rob_w has quit [Remote host closed the connection]
orivej has quit [Ping timeout: 264 seconds]
orivej has joined #picolisp
tankf33der has joined #picolisp
tankf33der has left #picolisp [#picolisp]
tankf33der has joined #picolisp
<tankf33der> o/
aw- has quit [Quit: Leaving.]
<beneroth> \o
<Regenaxer> Hi tankf33der, beneroth!!
<Regenaxer> tankf33der, I found a nasty bug in coroutines
<Regenaxer> to be exact, in environments in general
<tankf33der> released? i will test then.
<Regenaxer> will have to redesign the I/O frames
<Regenaxer> oh, no
<Regenaxer> not even started to fix
<Regenaxer> need different internal data structures
<Regenaxer> what is saved on the I/O stacks and in catch/throw/co/yield 'env' frames
<Regenaxer> Needs time
<Regenaxer> Current version segfaults if a coroutine is invoked in some I/O environment and later runs in a different one
<Regenaxer> Found the problem in the chess App
<Regenaxer> it uses coroutines tho have drawCanvas keep its state during animations
<Regenaxer> I presented the chess GUI on PilCon, but unfortunately almost nobody attended
<Regenaxer> We were just three in the end
<Regenaxer> Perhaps Saturday is not good?
<beneroth> give it another 1-2 attempts, I would say
<Regenaxer> yeah, I don't mind
<Regenaxer> It was fun
<beneroth> I didn't attend (as most times recently) because I either was busy/away at the time.. or sleeping from too much work ^^'
<Regenaxer> :)
<beneroth> so for me it's nothing to do with pilcon, I just didn't manage to come, sorry :(
<Regenaxer> no problem
<beneroth> next time would be 19th 1600 UTC ?
<Regenaxer> yes, or 17:00 CET
<beneroth> I would recommend keeping a fixed interval/date (versus finding a date each time)
<Regenaxer> on 19th
<beneroth> better have it regularly but then a few times a very short or small one, then to debate about dates
<beneroth> second one always ends up in "lets skip one" and... then skip forever eventually
<Regenaxer> For me anything is ok
<beneroth> well for us self-employed ones, Saturday might be family day while we can often arrange something on the weekday.. but for usual employed people it might be the other way round as picolisp falls into their "free time"
<beneroth> I don't mind. just lets keep a regular schedule
<Regenaxer> yeah, difficult
<Regenaxer> In the mailing list I got the impression that Sat is better
<beneroth> yeah I would also believe that Saturday should be better for most
<beneroth> not necessarily for the "core" community here in IRC.. aw-, tankf33der, mtsd, Nistur, you me...
<beneroth> but then again pilcon is more for the other ML people then the daily active users here, I would say :)
<beneroth> we could always hop on jitsi here anytime if there is a topic to discuss with screen or audio :)
<Regenaxer> T
Wiin has quit [Quit: Leaving]
<Regenaxer> Will need a few days for the pil21 change. Hope it will not break completely
<Regenaxer> Not today
<Regenaxer> And tomorrow I'm busy too, perhaps in the afternoon
<beneroth> yeah no worries :)
<Regenaxer> I *am* worried
<beneroth> because of pilbox? :/
<Regenaxer> it is a major redesign of a critical part
<Regenaxer> no, in general
<beneroth> you should write an email to the debian maintainer
<beneroth> to wait a bit longer if he not already switched to pil21
<Regenaxer> relevant only for coroutines
<Regenaxer> yeah
<beneroth> limited used
<beneroth> I would dare to say there is probably no major user of it besides you.. maybe aw-
<Regenaxer> I think he did not start yet
<beneroth> I have several planned use cases but didn't get around to use them yet
<Regenaxer> The current case cannot be done without coroutines I think
<Regenaxer> drawCanvas called from various places but keeping state
<Regenaxer> i.e a loop
<Regenaxer> driven by the browser (JS)
<Regenaxer> I explained in PilCon ;)
<Regenaxer> The chess GUI runs also in desktop browser
<Regenaxer> that's how I develop it
<Regenaxer> and then just stuff into PilBox
<Regenaxer> same code
<beneroth> I see
<beneroth> so was a good test case ;-)
<Regenaxer> yes, hardcore coroutines
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #picolisp
jibanes has quit [Ping timeout: 272 seconds]
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #picolisp
Blukunfando has quit [Remote host closed the connection]
jibanes has joined #picolisp
orivej has quit [Ping timeout: 240 seconds]
jibanes has quit [Ping timeout: 264 seconds]
jibanes has joined #picolisp
orivej has joined #picolisp
aw- has joined #picolisp
<aw-> beneroth: Regenaxer i don't/haven't used co-routines actually.. but i think tankf33der did some things with them