GTC: Major changes

[Sebastien Loisel <Sebastien.Loisel@Eng.Sun.COM>]

I made major changes to the networking code of GTC in the CVS. I was tempted to 
call this 0.3 but the changes are not apparent, there is still only the 
networked flying ducks demo. However, the good thing is that network related 
code in a game will now be very small, in my flyingducks demo, flyingducks.c has 
all network independant code and duckserver.c has all network related code and 
should be very tiny. Small modifications to happen soon will make this 
networking code even simpler. I next intend to take a bite out of texturing, 
which means I'll need meshes with textures (hint, hint). Once that's done, I'll 
call it 0.3.

As a side note, I'm planning to start testing with some heap sanity library (I'm 
thinking dmalloc, if you have a better idea, tell me). I don't think there are 
any problems with GTC now (perhaps a few "leaks", in the sense that some data 
which is meant to last through the lifetime of the program isn't freed) but it 
wouldn't hurt to keep tabs on these things.

Sebastien Loisel -- McGill University -- Sun Microsystems
http://www.math.mcgill.ca/~loisel/

*************************************************************
To unsubscribe, send an e-mail to majordomo@gtc.seul.org with
unsubscribe gtc-dev       in the body. http://gtc.seul.org/