Eclipse Community Forums: DSDP - Real-Time Software Components (RTSC) » How to handle error in Module

Help

Home

Home » Archived » DSDP - Real-Time Software Components (RTSC) » How to handle error in Module_startup()?

Show: Today's Messages :: Show Polls :: Message Navigator

How to handle error in Module_startup()? [message #1659]

Thu, 12 March 2009 18:55

Ramsey Harris

Messages: 22
Registered: July 2009

Junior Member

Champs,

What is the recommended way to handle and error in <<Mod>>_Module_startup()? Should I raise an error? Should I create a local error block and pass this to other modules? Should I always return NOTDONE when an error occurs?

Thanks
~ Ramsey

Report message to a moderator

Re: How to handle error in Module_startup()? [message #1705 is a reply to message #1659]

Mon, 16 March 2009 15:29

Dave Russo

Messages: 172
Registered: July 2009

Senior Member

Ramsey Harris wrote:
> Champs,
>
> What is the recommended way to handle and error in
> <<Mod>>_Module_startup()? Should I raise an error? Should I create a
> local error block and pass this to other modules? Should I always return
> NOTDONE when an error occurs?
>
> Thanks
> ~ Ramsey
Since startup occurs _very_ early, before main(), it is best to _never_
fail in startup. It's very difficult for a user to determine what the
problme is when their application never makes it to main().

You can set a flag in your startup to indicate the failure and then fail
"normally" in your modules API's due to a startup problem.

If, on the other hand, it is important that the application not proceed
if the startup fails, you can call System_abort().

Report message to a moderator

Previous Topic:	Problems with RTSC packages and legacy binary objects
Next Topic:	Is there handle up-casting in meta-domain?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 05:54:55 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter