From: Warren Young
Date: February 14 2005 4:21pm
Subject: Legacy exceptions in MySQL++ considered harmful
List-Archive: http://lists.mysql.com/plusplus/3975
Message-Id: <4210CFF7.9050801@etr-usa.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

I'm beginning to think that it's time that all the legacy exception 
stuff in MySQL++ should die.  It was created in a time long ago, when 
not all C++ compilers supported Standard C++ exceptions.  Now that we've 
moved the bar up so high w.r.t. compilers that we support, is this 
feature even necessary any more?

Removing this would have these benefits:

- exceptions.h.in would become a regular header, and half the code in it 
would go away.

- All that nasty conditional code in the examples would go away.

- The exception flag to the configure script would be the default.

- I could, in good conscience, accept Chris Frey's Row::operator[] at() 
patch.

Anyone have any complaints about doing this?  I think that I will make 
at least one release before doing this if there's no dissent, in order 
to get some other patches out separately.