On Dec 4, 2007 9:49 AM, François Cauwe <francois [..] ...> wrote:

> For my thesis I need some extra functionality in orocos, especially in
> kdl en bfl.
>
> In kdl most functions return a status code, which defines the error. I
> think the assert() command is depreciated.
>
> Bfl uses the assert() command.

Normally only where appropriate, see

If you think there are still cases where BFL shouldn't use assert,
please reopen the bug.

> So I was wondering, what is the recommended way to handle errors in
> orocos? Is there a orocos(real time?) way to throw and catch exceptions?

Concerning the RTT, you might want to have also a look at the error
states for taskcontexts Peter added in the 1.4 release, see

regards,

Klaas

On Tue, 4 Dec 2007, FrançoisCauwe wrote:

> For my thesis I need some extra functionality in orocos, especially in
> kdl en bfl.
>
> In kdl most functions return a status code, which defines the error. I
> think the assert() command is depreciated.
>
> Bfl uses the assert() command.
>
> So I was wondering, what is the recommended way to handle errors in
> orocos? Is there a orocos(real time?) way to throw and catch exceptions?
>
"assert" is meant to signal errors when you are developing and have set the
compiler to evaluate the assertions. You should not run your code with
assert-evaluation on during production use of the software.

Realtime error handling should be done via "events" (with a realtime policy
set for the event handling). The best you can do in a library is not to
fire these events directly, but let the application that uses your library
interpret the error code and do the appropriate event firing.

Herman

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm