ChanServ changed the topic of #picolisp to: PicoLisp language | Channel Log: | Check also for more information
xkapastel has quit [Quit: Connection closed for inactivity]
orivej has quit [Ping timeout: 276 seconds]
_whitelogger has joined #picolisp
_whitelogger has joined #picolisp
jibanes has joined #picolisp
jibanes has quit [Ping timeout: 265 seconds]
jibanes has joined #picolisp
<tankf33der> so picolisp could be used on sabotage linux
<tankf33der> except this select() change in 1.1.24:
<tankf33der> compatibility & conformance:
<tankf33der> - select no longer modifies timeout on failure (or at all)
<tankf33der> afk.
_whitelogger has joined #picolisp
<Regenaxer> tankf33der, yes, select() change is problematic
<Regenaxer> btw, in pil21 I don't use select() any longer, but poll()
_whitelogger has joined #picolisp
<DKordic> Shouldn't ""epoll"" be used on Linux?!
<Regenaxer> Better not. It is not portable, and I don't see any advantage
<Regenaxer> We don't need "edge-triggered" events in PicoLisp
<Regenaxer> do we?
_whitelogger has joined #picolisp
<DKordic> It can be configured as level-triggered too.
<Regenaxer> Why should we? What use case?
<Regenaxer> In terms of PicoLisp 'task's
<Regenaxer> Anyway it is useless for us, as it is Linux-only
<DKordic> What is ""pico"" of picoLisp?
<Regenaxer> Guess what
<aw-> _PI_co Lisp is not _CO_mmon Lisp
<Regenaxer> Hi aw-! :)
<aw-> hi
_whitelogger has joined #picolisp
orivej has joined #picolisp
orivej has quit [Ping timeout: 250 seconds]
freemint has joined #picolisp
freemint has quit [Ping timeout: 240 seconds]
orivej has joined #picolisp
beneroth has quit [Quit: Leaving]