on 1/31/03 11:05 PM, Eric Forget at forgete (at) cafederic DOT com wrote:
>> In 2.0 I am going workaround this problem of compilers by using interface
>> classes...although problem of exceptions still remain...
>
> I think you should remove all the exceptions and having return code instead.
> It is less dangerous and let the user of your library design its software as
> he wants. You can always have a macro like: ThrowIfVDKErr_() which will
> throw but only the user want it.
Problem is that exceptions provide MORE effective way that error return,
And constant check of error code in if(). I do not think that err code is
less dangerous. In fact you can ignore it. You cannot simply ignore
exception.
This is why I have choose exceptions.
Of course may be it is possible
A) throw exceptions in kernel
B) catch them on top level of kernel and convert into err code.
C) all pure interface classes do not throw but only return errors...
>> I many times already think and wonder, why they will not make ANSI standard
>> on C++ binary as this was on C language...We'd get paradise.
>
> I agree. But for frameworks it is still a problem with version. As soon as
> you add a member or a member function, you need a completely new framework
> version if you don't want all your customer having to recompile...
Headache in fact. :-)
--
Best regards,
Ruslan Zasukhin [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan@paradigmasoft.com
web: http://www.paradigmasoft.com
To subscribe to the Valentina mail list go to:
http://listserv.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------
_______________________________________________
Valentina mailing list
Valentina (at) lists DOT macserve.net
http://listserv.macserve.net/mailman/listinfo/valentina
©2003 Ruslan Zasukhin |
