On 11/08/2014 16:03, Dmitry Yemanov wrote: > > We either forget about exceptions completely, or throw some partially > abstract class (thus forcing users to implement the exception before > being able to compile), or maybe go for the policies you described. > > That said, I'd rather resolve the other issues first. Even a > no-exception API may be "good enough" for the time being, we can offer > something better later. > > One of the current problems (not major, but surely a problem) is the manual usage (init, set, catch, throw) of IStatus in our code.
An integrated approach (who throws from IStatus, catchs and set IStatus) is very welcome. However, there is a prerequisite for this. IStatus should well manage its memory. I had to use circularAlloc in DdlNodes.epp because of its problems, and this is very bad. I'm afraid of all QualifiedName::toString calls. Adriano ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
