|Message: Re: memory management of G4VUserTrackInformation||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
> [in G4VUserTrackInformation.hh] > // Concrete class derived from this class MUST use G4Allocator > // for memory management
Hmmm. I had not noticed this, and am about to use G4VUserTrackInformation, so I would like an answer to this, too.
The standard way to do something like this in C++ is to give G4VUserTrackInformation its own operator new and operator delete functions (presumably using G4Allocator), and to caution the user not to override them. The reason this is important is because ~G4Track() is supposed to delete the G4VUserTrackInformation of the track, and it needs to know how to do that.
Looking at the code, it appears to me that this comment is incorrect: ~G4Track() merely does delete fpUserInformation, and that is ultimately going to call G4VUserTrackInformation::operator delete. That delete operator is not defined, and will therefore be the default delete operator. So as long as you don't override operator delete you'll get the one from G4VUserTrackInformation, and that should be just fine.
Has anybody actually used G4VUserTrackInformation? What really happens?
|Inline Depth:||Outline Depth:||Add message:|