>
>As above, the reason I don't like this type of solution is the fact that the calling routine may *not* check the return value.
>OK - *you* know you should and you will probably remember. Others users of the routine are more likely to forget. That said, it's a pretty standard pattern in Windows in general....
Funny thing but you were right. I was just changing another routine (only 10 minutes after the initial discussion) and already almost forgot that I need to "deal" (e.g. pass) the error string and check the value of the data set in the calling routine.
So I can see that it would be nice to throw exception right in the called routine. I will see how and if it can be done.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
