quakeforge/ruamoko/lib/cbuf.r

#include <cbuf.h>

void Cbuf_AddText (cbuf_t cbuf, string text) = #0;
void Cbuf_InsertText (cbuf_t cbuf, string text) = #0;
void Cbuf_Execute (cbuf_t cbuf) = #0;
void Cbuf_Execute_Sets (cbuf_t cbuf) = #0;
[libr] Treat ruamoko headers as system headers Now that qfcc actually supports them properly. 2020-03-03 06:24:41 +00:00			`#include <cbuf.h>`
bring in most of the remaining api bits from cs-code (except string and stringh: I'm not really that keen on those interfaces and I'ld like to see them go away) and create libcsqc for most of it (key goes into gui) 2002-08-16 20:15:10 +00:00
[qfcc] Add a handle type for engine resources I never liked the various hacks I had come up with for representing resource handles in Ruamoko. Structs with an int were awkward to test, pointers and ints could be modified, etc etc. The new @handle keyword (@ used to keep handle free for use) works just like struct, union and enum in syntax, but creates an opaque type suitable for a 32-bit handle. The backing type is a function so v6 progs can use it without (all the necessary opcodes exist) and no modifications were needed for type-checking in binary expressions, but only assignment and comparisons are supported, and (of course) nil. Tested using cbuf_t and QFile: seems to work as desired. I had considered 64-bit handles, but really, if more than 4G resource objects are needed, I'm not sure QF can handle the game. However, that limit is per resource manager, not total. 2023-05-25 01:41:28 +00:00			`void Cbuf_AddText (cbuf_t cbuf, string text) = #0;`
			`void Cbuf_InsertText (cbuf_t cbuf, string text) = #0;`
			`void Cbuf_Execute (cbuf_t cbuf) = #0;`
			`void Cbuf_Execute_Sets (cbuf_t cbuf) = #0;`