------=_Part_8995_30167820.1144083064239
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I am using MySQL 5.0.19 and MySQL++ 2.1.0 under Visual Studio 7.1.

The following code compiles with an error:

#include <mysql++.h>
#include <custom.h>

int main(int argc, char* argv[])
{
return 0;
}


The errors:

error C2010: '.' : unexpected in macro formal parameter list
error C2010: '.' : unexpected in macro formal parameter list
error C2010: '.' : unexpected in macro formal parameter list

I am including custom.h in order to use the sql_create_2 macro.

Tim

------=_Part_8995_30167820.1144083064239--

Tim Stewart wrote:
Alas, this is because VC++ 2003 doesn't support variadic macros, used by
a new feature in MySQL++ v2.1. That feature allows you to #include a
file containing an SSQLS definition in multiple modules and avoid a
linker error resulting from the static variable definitions in some
SSQLS macros.

In the upcoming MySQL++ v2.1.1, I've added a feature to custom.pl to
disable this feature, which will fix this problem. You will need a Perl
interpreter to run the custom.pl script. Alternately, you can manually
hack out the MYSQLPP_SSQLS_NO_STATICS stuff in custom.h and custom-macros.h.

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

------=_Part_21107_12227449.1144247588635
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Thanks, Warren!

I had hoped to use the sql_create_X macros. Do I need to upgrade to Visual
C++ 2005?

Thanks again!

On 4/4/06, Warren Young <mysqlpp (AT) etr-usa (DOT) com> wrote:
------=_Part_21107_12227449.1144247588635--

Tim Stewart wrote:
Please re-read what I wrote, and the v2.1.0 change log entry. This new
feature only makes it possible to use SSQLS in broader contexts than
before. If you cannot use the feature, you get to use SSQLS with the
same limitations that we dealt with on all platforms.

Well, plainly there are compensations.

I'm curious: why aren't you on MSDN? I ask only to more broadly
understand the situation of the MySQL++ user base.

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

------=_Part_21664_24217898.1144253201972
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

My companies products all are built under Visual C++ 2003. We will
eventually upgrade to 2005 but it hasn't happened yet.

On 4/5/06, Warren Young <mysqlpp (AT) etr-usa (DOT) com> wrote:
------=_Part_21664_24217898.1144253201972--