![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
The const_string.h one undefines min and defines NOMINMAX. An alternative to this is to define NOMINMAX in the bakefile project creation, but this doesn’t fix problems when people include const_string.h in their projects. The README patch adds a little extra info. The query.ccp patch presents the alternative solution for the memory leak, that we talked about some time ago. |
#2
| |||
| |||
|
|
-----Original Message----- From: Warren Young [mailto:mysqlpp (AT) etr-usa (DOT) com] Sent: 22 December 2006 14:05 To: MySQL++ Mailing List Subject: Re: A couple of patches Matt Dargavel wrote: The const_string.h one undefines min and defines NOMINMAX. An alternative to this is to define NOMINMAX in the bakefile project creation, but this doesn't fix problems when people include const_string.h in their projects. The README patch adds a little extra info. The query.ccp patch presents the alternative solution for the memory leak, that we talked about some time ago. Sorry for the delay in getting back to you on this. I just set it aside for consideration, and only later realized that the patches aren't actually attached. Don't bother with the min/max one. I know what's going on there, and am taking that up separately. -- MySQL++ Mailing List For list archives: http://lists.mysql.com/plusplus To unsubscribe: http://lists.mysql.com/plusplus?unsub=matt@shout- telecoms.com |
#3
| |||
| |||
|
|
-----Original Message----- From: Matt Dargavel [mailto:matt (AT) shout-telecoms (DOT) com] Sent: 22 December 2006 16:22 To: plusplus (AT) lists (DOT) mysql.com Subject: RE: A couple of patches No worries about the delay- took me long enough to get them done! :-) According to my sent items the patches were there, but here's the query patch and README patch again. Let me know if they don't arrive. These patches are based on today's svn, although I don't think they've changed from the last lot. Merry Christmas! Matt. -----Original Message----- From: Warren Young [mailto:mysqlpp (AT) etr-usa (DOT) com] Sent: 22 December 2006 14:05 To: MySQL++ Mailing List Subject: Re: A couple of patches Matt Dargavel wrote: The const_string.h one undefines min and defines NOMINMAX. An alternative to this is to define NOMINMAX in the bakefile project creation, but this doesn't fix problems when people include const_string.h in their projects. The README patch adds a little extra info. The query.ccp patch presents the alternative solution for the memory leak, that we talked about some time ago. Sorry for the delay in getting back to you on this. I just set it aside for consideration, and only later realized that the patches aren't actually attached. Don't bother with the min/max one. I know what's going on there, and am taking that up separately. -- MySQL++ Mailing List For list archives: http://lists.mysql.com/plusplus To unsubscribe: http://lists.mysql.com/plusplus?unsub=matt@shout- telecoms.com |
#4
| |||
| |||
|
|
Hmm, I see- no patches on the delivered message for some reason. |
|
+ To get bakefile to create the makefiles necessary for each + platform, simply run bakefile_gen in the project root. |
|
Query::Query(Connection* c, bool te) : -#if defined(_MSC_VER) -std: stream(std::_Noinit), // prevents a double-init memory leak in RTL-#else -std: stream(0),-#endif +std: stream(&sbuffer_),OptionalExceptions(te), Lockable(false), def(this), @@ -42,7 +38,6 @@ conn_(c), success_(false) { - init(&sbuffer_); |
#5
| |||
| |||
|
|
+ To get bakefile to create the makefiles necessary for each + platform, simply run bakefile_gen in the project root. No, this isn't right. First off, bakefile_gen shouldn't ever be run directly. Use the rebake or bootstrap wrapper scripts instead. What problem are you trying to solve here? Is it the "I just checked out from svn and it doesn't work" case? If so, that's handled by running the bootstrap script, which is already covered in the HACKERS file. |
|
I thought we shot this one down because it's technically illegal in C++. It's not guaranteed that sbuffer_ is initialized before the base class ctors are called. It may work on current compilers, but what about the future? Yes, I'm not entirely sure of the best way. The reason I suggested this |
![]() |
| Thread Tools | |
| Display Modes | |
| |