Re: [info-performer] Allocating classes from shared memory

From: Goncalo Nuno Moutinho De Carvalho (C3099023++at++tees.ac.uk)
Date: 09/25/2003 04:41:45

• Next message: Anthony Clare: "[info-performer] Texturing"
• Previous message: Simone Herrmann: "[info-performer] Analogon to glPolygonMode"
• Maybe in reply to: Dimi: "[info-performer] Allocating classes from shared memory"
• Next in thread: Marc Mendez: "Re: [info-performer] Allocating classes from shared memory"

pfHey,

>I ve written a C++ app here that required to redefine >the operator new()
>for every object to remove the messages "Can't free >non PF memory"
>although every object was deriving pfObject.

Well, operator new is inherited when you derive. I believe for pfMemory objects operator new is overloaded
to use the shared arena. I certainly derived a lot of new nodes from existing ones and didn't have any problems in multiprocessing mode. The same think happened with pfObject if I'm not mistaken. But then most of the times I don't need to delete them.

In what context do you get that message?

Goncalo

• Next message: Anthony Clare: "[info-performer] Texturing"
• Previous message: Simone Herrmann: "[info-performer] Analogon to glPolygonMode"
• Maybe in reply to: Dimi: "[info-performer] Allocating classes from shared memory"
• Next in thread: Marc Mendez: "Re: [info-performer] Allocating classes from shared memory"

This archive was generated by hypermail 2b29 : Thu Sep 25 2003 - 04:46:20 PDT