Bill Currie d13ce81b4f Ensure the type's encoding string is valid. ... When encoding a type to a qfo file, the type's encoding string is written and thus needs to be valid prior to actually doing the encoding. The problem occurs mostly in self-referential structs (particularly, obj_class) because the struct is being encoded prior to the pointer to the struct.		2012-11-11 20:22:48 +09:00
..
doc	Add an extended mode to qfcc.	2012-07-14 17:16:33 +09:00
include	Ensure the type's encoding string is valid.	2012-11-11 20:22:48 +09:00
source	Ensure the type's encoding string is valid.	2012-11-11 20:22:48 +09:00
test	Rework the unary_expr grammar to allow ++*foo.	2012-11-09 12:32:38 +09:00
AUTHORS	more mailing list corrections	2003-07-12 21:50:22 +00:00
bootstrap	scary, but the only changes qfcc needed to build as part of quakeforge was	2002-01-22 05:48:03 +00:00
configure.in	fix CPP_NAME for independently built qfcc	2002-06-04 20:43:11 +00:00
Makefile.am	Do an audit of the Makefile.am files.	2012-02-07 16:04:19 +09:00
TODO	Update TODO.	2011-02-22 12:23:00 +09:00