06:17Lyude: skeggsb: would you be ok with me using the twod engine for creating black fbs for the core surface? I've currently got atomic states with only ovly/cursor enabled (and base disabled) working with a black fb we allocate with the atomic state, but I'm thinking it'd probably be nice if we could fill it out as black using the gpu instead of having to map it and use the cpu
06:20Lyude: was thinking of sharing some of the code we've currently got using it for fbcon
06:20Lyude: (but moving it out of fbcon to somewhere more appropriate of course)
06:21Lyude: erm, *currently got using it in fbcon (like nvc0_fbcon.c)
20:18karolherbst: who came up with "twod" anyway...
20:18karolherbst: the name I mean
20:18imirkin: probably the same person who came up with threed
20:19imirkin: identifiers in C (and most languages) can't start with a digit
20:19imirkin: so i expect there was some advantage to naming it twod vs 2d
20:21karolherbst: suffering from missdesigned literals :/ annoying
21:39RSpliet: Not denying that this limitation couldn't've been fixed in the 47 years that followed, but "misdesigned" implies the state of the art in 1973 was definitely such that compilers could easily be built otherwise. I wasn't there (in fact, I was minus 15 years old) , but I have my doubts.
21:40RSpliet: That being said, I would have definitely doubled down on these identifiers and called it twodee/threedee :-P
21:41imirkin: or toodee and treedee?
21:45RSpliet: If ever a 2.5D engine was implemented for games like Sim City and Civilisation, I'd defo call it twofiddy
21:49imirkin: RSpliet: that'll be about twofiddy
22:04karolherbst: RSpliet: well, you could also just not have literal modifiers
22:04karolherbst: because.. when are they actually useful and not just an annouence
22:05karolherbst: and they cause bugs anyway