Re: caGateway crashes / use of *MustSucceed functions

[Dirk Zimoch <dirk.zimoch@psi.ch>]

> [...] One exception frequently cited is when
> starting an IOC its maybe ok, but if this occurs in common library code then
> it's probably going to be used inappropriately in other situations, and
> surely eventually we will need to upgrade allowing online add and delete of
> records and then it's less clear when iocInit starts and ends? 
This show why C++ exceptions are better than the good old C abort(). If 
creation of a new record fails because of insufficient memory, an 
exception can be thrown. During run-time it should be caught and an 
error should be reported to the user that the record can't be added to 
the system. During initialization, it may be acceptable not to catch the 
exception which will in the end call abort(). Thus the application 
developer and not the support library developer decides if the 
application (here the ioc) must die or not.
By the way, if creation of a record fails because of a typo in a 
template file, the ioc happily continues starting up, but with one or 
many records missing -- even though this *is* a programming error, not a 
run-time problem.
Dirk