|Message: Re: Using shared_ptr (from the boost library)||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)|
Hi Peter, > In my application, I usually do a lot of "new", espescially in the > detector construction: New Elements, new Material Properties, new > volumes, etc. > > Then, before returning the physical world volume, I lose all these > pointers, as they go out of scope: materials and geometrical volumes/solids are 'cached' and registered in stores internally in Geant4. These pointers are de-registered and deleted at the end of the application if not explicitly done by the user. If an exception occurs, no tiding up is done implicitly by the Geant4 kernel... btw, you certainly don't want to delete the pointers within the construct() method... you may want to keep the pointers as members of the class, or implement a way to cache them if wish to reuse them elsewhere within the lifetime of your DetectorConstruction object. Gabriele
|Inline Depth:||Outline Depth:||Add message:|