Stephan Witt wrote:

> Yes, it didn't work. I had to remove the const keyword to get it to
> compile. Yesterday I couldn't figure it out.

Yes, this is the standard way to catch exceptions (unless you work with 
libraries that ignore the standards and define their own thing, like the 
Microsoft Foundation Classes which require to catch exceptions by pointer 
and to call a Delete() method). But I did not notice that eitehr when 
looking at your patch.

> But the message text is empty nevertheless.
> 
> I put the improved version in, thank you.

Very good! Now it is the responsibility of enchant to create a more sensible 
error message.


Georg

Reply via email to