|Message: Re: error linking linac example when it is modified to read iaea files||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)|
A normal use of G4Exception is this:
- originOfException: Text including class name and method name. (e.g.: "G4IAEAphspReader::G4IAEAphspReader()") - exceptionCode: Text with an error code (whatever format as long it is text); e.g.: "IAEAphspReader0001" - Severity and description look ok to me.
Then, in your case, should that exception is thrown, then the description message would appear twice, which is not the regular way of coding it. But, that will only affect on how the exception is described on output. It will _not_ affect the functioning of the class itself, as an exception is thrown there is something wrong or unexpected during the program execution. So, probably, you should worry about something else, not the exception description itself :-)
Also, you picked the lowest severity level (JustWarning) which means that the code would follow through. Maybe this particular one deserved higher severity, but a throwing a warning is also ok.
In short, the code should work smoothly. If an exception is thrown, the message will not be standard. That's all.
Hope it helps, Miguel
|Inline Depth:||Outline Depth:||Add message:|