adamcstephens has quit [Remote host closed the connection]
adamcstephens has joined #river
alexherbo2 has joined #river
alexherbo2 has quit [Remote host closed the connection]
belanthor has joined #river
Keeto has joined #river
Cornelius-Figgle has quit [Ping timeout: 252 seconds]
Cornelius-Figgle has joined #river
Keeto has quit [Ping timeout: 265 seconds]
Keeto has joined #river
belanthor has quit [Quit: Leaving]
mtm has quit [Ping timeout: 265 seconds]
mtm has joined #river
Keeto has quit [Ping timeout: 265 seconds]
<leon-p>
the approach I came up with in france for the next_event() function of my library is lovely and all, but the more I work with it, the more I long for just having a struct of callback function pointers...
notchoc has joined #river
twelve has joined #river
elshize has joined #river
twelve has quit [Remote host closed the connection]
twelve has joined #river
<ifreund>
I haven't tried to use wayland that way before
<ifreund>
I think the relative ergonomics of the two approaches will depend mostly on the language
Keeto has joined #river
<leon-p>
from a users PoV it's not very different, especially since the guile bindings abstract that mechanism far enough away, that you can't even tell which of the two is used (it's all just hooks when you're writing scheme)
<leon-p>
however when adding new events to the library, it's a lot more annoying
<leon-p>
(especially since I needed to do unholy struct castings of unions to make guiles not very powerfull FFI work)
<leon-p>
so I think I'll switch to callbacks for now
elshize has quit [Ping timeout: 260 seconds]
twelve has quit [Remote host closed the connection]