if you really target MASSIVE MULTIPLAYER as it was stated some time with =
Arianne, then you probably cannot copy everything around.
With pointerbased languages, yes it's hard to organise...
Maybe i have a suggestion, since i'm not doing C (pythonist) i can't =
really tell if this is useful.
Creating a mediator in between datastructure and program. Whenever =
something wants to keep the data, it shall tell the mediator and =
register. The program will work with a pointer to the mediator. This =
mediator will forward the data upon request. When the program doesn't =
need the data anymore, it will deregister.
Yes, you're right, when i remember to deregister, then i can also =
remember to check for releasing the memory. But when i notice that i =
forgot it somewhere, then i can ask mediator who didn't deregister.
Von: Miguel Angel Blanch Lardin =
Gesendet: Mi 22.01.2003 11:44
Betreff: Re: [Arianne-general] Code updates.... and request for some =
help... again :)
I am sad of reading this.
By this change Arianne will get a help more unstable and harder to =
Before the code you have been changing lately, we used to use pointers =
for objects what resulted on a real chaos of memory leaks.
I would change it to somekind of shared pointers on the WORST case, but =
sure that Object is still the way to go.
Add photos to your e-mail with MSN 8. Get 2 months FREE*.=20
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
Arianne-general mailing list