If you're making the assumption that its an IA32 machine, you are very safe in making a 32 bit int assumption as well. (Windows & Linux both)
david -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Jim Hunter Sent: Tuesday, June 11, 2002 10:35 AM To: [EMAIL PROTECTED] Subject: Re: Re: [hlcoders] A method for creating new user variables > come across 64bit pointers. On the other hand, it is not > guaranteed that an int will be 32bit large. So your code is living > on some assumptions not necessarily true. Good point - I hadn't thought of that. > WRITE_ function. Sending byte by byte has the advantage that you > don't have to change the Send function when you change the > structure. Also a good point. > Since you said that you add a structure as a member I don't see > where the dynamic memory allocation comes in. Unless you allocate > the structure dynamically. But you could take care of that by The dynamic memory allocation only exists on the client side to allow for an arbitrary number of predicted frames to coexist. On the server, the structure is a permanent member of CBaseEntity. Thanks for the comments. :) Jim _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
