Adding an error message string to Backend

[Matthew Vanecek]

--=-JTwqSU8/PylDy5zJUm6/
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

I'm planning on adding a char * errorMessage to the Backend struct.=20
This will provide the Backend a method for communicating a meaningful
error message to the GUI, via the PWARN_GUI macro.  I'll also add the
xaccBackendSetMessage() and xaccBackendGetMessage() functions.  This is
immediately useful to me in the SQL backend, but should provide benefits
to the other backends as well.

This should probably be looked at as a bug fix. ;)

If there are no objections, I'll submit the patch by Thursday to apply
to CVS.

Thanks,
--=20
Matthew Vanecek
perl -e 'print $i=3Dpack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
***************************************************************************=
*****
For 93 million miles, there is nothing between the sun and my shadow except=
 me.
I'm always getting in the way of something...

--=-JTwqSU8/PylDy5zJUm6/
Content-Type: application/DEFANGED-57; name="signature_asc.DEFANGED-57"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQA90dxYOMmiB1jXEBsRAtFPAJsE8tAOeWy+PQdzInoAymyNz3ZAgwCeP6eV
VTJ2FvZcYaTQqbBQ58Dsra0=
=OnE0
-----END PGP SIGNATURE-----

--=-JTwqSU8/PylDy5zJUm6/--