Hi.
I see that OSG does not use exceptions, instead it only notifies of
errors. Does it mean, that OSG encourages return-code error handling?
Currently I use exceptions (which are only thrown if application
cannot continue normal operation: invalid resource, invalid input
parameter, etc) and would
HI Michael,
On 12 June 2012 07:59, michael kapelko korn...@gmail.com wrote:
I see that OSG does not use exceptions, instead it only notifies of
errors.
The majority of the OSG doesn't use exception. It used to use more
but I did a purge of use of exceptions in the core OSG to avoid
problems
I've come up with 3 types of errors:
1) constructor failure;
2) missing resource file;
3) invalid function parameter.
How does OSG handle all these cases exactly? You mentioned a feedback
on errors in file loading case, is it about 2)? Can you please
summarize techniques for each of the errors?
On 12 June 2012 14:46, michael kapelko korn...@gmail.com wrote:
I've come up with 3 types of errors:
1) constructor failure;
2) missing resource file;
3) invalid function parameter.
How does OSG handle all these cases exactly? You mentioned a feedback
on errors in file loading case, is it
4 matches
Mail list logo
