16:47:11mfianoBike: I'm not sure if this helps. Maybe I misinterpretted your question: https://git.mfiano.net/mfiano/freebsd-ffi/src/branch/main/src/ffi-enums.lisp#L5
16:57:21Bikethanks, but yeah, looks like you're just doing synonyms here
16:57:54mfianoBut with offsets which is what I thought you wanted.
16:58:29mfianoAnyway, I'm no cffi expert either. I haven't done much with bitfields before.
17:04:51Bikewhat i basically want is a bitfield except some of the fields have multiple bits.
17:04:58Bikenot all that coherent, but that's what the header wants
17:05:48mfianoAh so not sparse, just variable width fields.
17:45:12Bikeapparently i need to brush up on cffi use generally, because for some reason the grovel bitfield is defining every field as -1
17:47:03Bikeis there a way to look at the temporary c and lisp files the groveler makes? or should i look for a problem elsewhere?
17:48:02Bikeah, just calling process-grovel-file works, ignore me
17:49:48Bikei guess the asdf integration suppresses the missing definition warnings.
18:35:30utisi'm getting an error from charms when i've closed a tmux window and reconnected: (cl-charms::%cehck-status -1 :error-message "Error in curses call from function cl-charms/low-level:mvwaddstr (received err).") does anyone happen to know what the problem is?
18:36:33utis(i.e. i've closed the terminal window and expected that that shouldn't affect the tmux pane)
22:46:47ashlnI'd like to read a constant number of bytes from a stream (or until EOF), like the interface provided by read(2). Is the only interface to binary file reading to do so one byte at a time with read-byte?