Am Donnerstag, 16. November 2006 19:48 schrieb Dennis Schridde: > Am Donnerstag, 16. November 2006 15:30 schrieb Roman: > > Author: troman > > Date: Thu Nov 16 15:30:29 2006 > > New Revision: 488 > > > > URL: http://svn.gna.org/viewcvs/warzone?rev=488&view=rev > > Log: > > Scripting engine overhaul - Part I > > -compiler and parts of interpreter now use union to store different data > > types -got rid of a great deal of pointer->integer casts > > > > -ASSERT() now outputs last event (or function) called by scripts > > -implemented float data type support for the scripting engine - basic > > functionality at the moment > > 1st: I get compilation errors: > > [67/209] * cc : ../lib/script/codeprint.c -> debug/lib/script/codeprint.o > In file included from ../lib/script/codeprint.c:7: > ../lib/framework/frame.h:99: warning: unused parameter ‘uword’ > ../lib/framework/frame.h:110: warning: unused parameter ‘sword’ > ../lib/framework/frame.h:121: warning: unused parameter ‘udword’ > ../lib/framework/frame.h:135: warning: unused parameter ‘sdword’ > ../lib/framework/frame.h:149: warning: unused parameter ‘fract’ > ../lib/script/codeprint.c: In function ‘cpPrintProgram’: > ../lib/script/codeprint.c:415: warning: assignment from incompatible > pointer type > ../lib/script/codeprint.c:425: error: invalid operands to binary - > ../lib/script/codeprint.c:435: error: invalid operands to binary - > ../lib/script/codeprint.c:457: warning: zero-length printf format string > ../lib/script/codeprint.c:462: error: invalid operands to binary - > ../lib/script/codeprint.c:469: warning: zero-length printf format string > ../lib/script/codeprint.c:476: error: invalid operands to binary - > ../lib/script/codeprint.c:483: warning: zero-length printf format string > ../lib/script/codeprint.c:488: error: invalid operands to binary - > ../lib/script/codeprint.c:538: error: invalid operands to binary - > ../lib/script/codeprint.c:542: error: invalid operands to binary - > ../lib/script/codeprint.c:546: error: invalid operands to binary - > Compilation failed > > > 2nd: Could you better spell out the namings? I know this is not your fault > in this particular case, but I had no clue what .v.bval shall be (eg). > Maybe .Value.Bool or similar would have been better... (Or .value._bool or > whatever.) > > Generally I think we all should keep an eye on the namings of our stuff. It > might me less to type, but it makes the code much harder to read if we only > use s, v, a, b and other very descriptive namings. > > --Dennis PS: What is oval???
pgpZWzF7edLWn.pgp
Description: PGP signature
_______________________________________________ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
