SGksIERlYXIgYWxsOg0KDQpJIGhhdmUgZG93bmxvYWRlZCBteX NxbCsrMS43LjkgZnJvbSAgd3d3
Lm15c3FsLmNvbS9kb3dubG9hZHMvYXBpLW15c3FsKysuaHRtbC BhbmQgcGF0Y2hlZCBpdCB3aXRo
IG9tbmlidXMtZ2NjLTMuMy5wYXRjaC5neiBhbmQgdGhlbiBidW lsdCBhbmQgaW5zdGFsbGVkLiBF
dmVyeXRoaW5nIGlzIE9LIGZvciBidWlsZGluZywgYnV0IGFmdG VyIEkgYnVpbGRpbmcgbXkgYXBw
bGljYXRpb24gdXNpbmcgbXlzcWwrKyBhcGkgYW5kIHJ1biB0aG UgYXBwbGljYXRpb24sIEkgZmlu
ZCB0aGF0IHRoZSBvcGVyYXRvcltdIG9mIGNsYXNzIFJvdyBoYX MgdGhlIGZvbGxvd2luZyBwcm9i
bGVtOiBVc2luZyB0aGUgdGhlIGZpZWxkIG5hbWUgaW5zdGVhZC BvZiBmaWVsZCBpbmRleCB0byBy
ZXRyaWV2ZSB0aGUgZmllbGQgdmFsdWUgaXMgbm90IHJpZ2h0Li BGb3IgZXhhbXBsZToNCg0KZHdV
c2VySUQgPSByb3dbIlVzZXJJRCJdLCBkd1VzZXJJRCBhbHdheX MgZ2V0cyAxMTUoaW4gZmFjdCwg
YW55IG90aGVyIGZpZWxkIGlzIGFsc28gMTE1KQ0KDQpidXQgd2 l0aCB0aGUgZm9sbG93aW5nIHN0
YXRlbWVudCwgZXZlcnl0aGluZyBpcyBPSzoNCg0KZHdVc2VySU Q9cm93WzBdDQoNCldoYXQncyB0
aGUgbWF0dGVyPyBJcyB0aGVyZSBhbnkgb3RoZXIgcGF0Y2ggbm VlZGluZyB0byBiZSBpbnN0YWxs
ZWQ/DQoNCkJlc3QgUmVnYXJkIQ0KWW91cnMgU2luY2VyZWx5IFRvbW 15

Tommy Tang wrote:

Why are you bothering with such an old version? It sounds like you're
new to MySQL++, so why not use the current version?

The only reason I still offer the GCC 3.3 omnibus patch is for those
unfortunates who have code that does not build under the current
version, but which must use GCC 3.3. If you do have such code, it's
usually easier to make the changes to your code to work with the current
library than to continue fighting with 1.7.9.

We're not interested in fixing any problems with 1.7.9. Or rather, we
already have fixed those problems, and the current version is that fix.

Note well: the behavior of that feature changed in 1.7.10.

--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw