No problem Joel, I understand your point.
There are different levels of suggestions. Sometimes they come with
resolutions and sometimes they don't. But the absence of a solution
doesn't mean suggestions or constructive criticism shouldn't be offered.
I will freely admit that I don't have a good alternative for a
different method to handle ssqls. That is clearly a tough problem.
My suggestion for the author is to try to find a solution for ssqls
that don't involve macros. If that can be done items #1 (macros are
tough to debug), #2 (no need for a perl script to generate the
macros), and #3 (the MYSQLPP_SSQLS_NO_STATICS should not be needed),
and #4 (no need for a workaround to #1) should go away.
Warren is clearly one of the experts and his help has been
appreciated. The intent was not to aggravate him or any other mysql+
+ developer. I hope that's understood. I'll make an effort to be
gentler with suggestions and criticisms.
On Aug 14, 2007, at 2:41 AM, Joel Fielder wrote:
> Graham Reitz wrote:
>> Any library even the c++ standard libraries should be able to and
>> eager to receive criticism from time to time.
> Just a general comment, I think everyone knows that there's stuff that
> can be done better (particularly Warren as he's pretty much the only
> active developer). Of more use would be *how* we can make things
> rather than simply listing *what* we've done wrong. How would you
> each problem you've highlighted?
> I hate clichés, but "don't bring me a problem unless you've got a
> solution" would seem to summarise my point more than adequately!
> I can see you suggested RAII for blob, I'm just making a general
> MySQL++ Mailing List
> For list archives: http://lists.mysql.com/plusplus
> To unsubscribe: http://lists.mysql.com/plusplus?