List:MySQL++« Previous MessageNext Message »
From:np Date:July 18 2005 1:52pm
Subject:Re : Re: VS 2003 / Mysql++ 1.7(or 2.0 b) =>__int64 followed by
'long'is illegal ???
View as plain text  
Hello, Is it possible to put mysqlpp::Connection * con in a class (and a .h) ?

I've tried already and then theses previous errors appears under VS 2003 ...

Sample code (.h):

#include <mysql++.h>
class VDO_Track_DM_Main {
public :
	mysqlpp::Connection * con; //  each object contains a single connection
	mysqlpp::Query * qry;
...
};

Have you already a sample compiled under VS 2003 and coded like this ?


Thanks for your help.


NP.




> ---------- Message d'origine -----------
> Expéditeur : np@stripped
> A : mysqlpp@stripped
> CC : plusplus@stripped
> Date : Tue, 12 Jul 2005 15:40:04 +0200
> Objet : Re : Re: VS 2003 / Mysql++ 1.7(or 2.0 b) =>__int64 followed by 'long'is
> illegal ???
> ...\mysql++\lib\defs.h(53): error C2632: '__int64' followed by 'long' is illegal
> 
> ...\mysql++\lib\defs.h(53): warning C4091: 'typedef ' : ignored on left of 'unsigned
> __int64' when no variable is declared
> 
> compiling command line found in C++ project properties is :
> /Od /G7  "Application_MS\mysql_src\include" /I "Application_MS\mysql++\lib" /I
> "Application_MS\jasper\include" /I "C:\test\SRC\Application_MS\mysql_src\include" /I
> "C:\test\SRC\Application_MS\mysql++\lib" /I "C:\test\SRC\Application_MS\jasper\include" /D
> "WIN32" /D "_WINDOWS" /D "_DEBUG" /D "_AFXDLL" /D "_MBCS" /Gm /EHsc /RTC1 /MDd
> /Yu"stdafx.h" /Fp"Debug/testApp.pch" /Fo"Debug/" /Fd"Debug/vc70.pdb" /W3 /nologo /c /ZI
> /TP
> 
> 
> 
> NP.
> 
> 
> 
> > ---------- Message d'origine -----------
> > Expéditeur : Warren Young <mysqlpp@stripped>
> > A : MySQL++ Mailing List <plusplus@stripped>
> > CC : 
> > Date : Mon, 11 Jul 2005 16:47:11 -0600
> > Objet : Re: VS 2003 / Mysql++ 1.7(or 2.0 b) => __int64 followed by 'long'is
> 	illegal ???
> > np@stripped wrote:
> > 
> > > i have a compile error in defs.h :
> > 
> > Please post the text of the compiler error.
> > 
> > > If i try to force NO_LONG_LONGS macro, 
> > 
> > Why would you do that?  For standard platforms, NO_LONG_LONGS should be 
> > defined correctly from within platform.h.  There should be no good 
> > reason to change it manually.
> > 
> > -- 
> > MySQL++ Mailing List
> > For list archives: http://lists.mysql.com/plusplus
> > To unsubscribe:    http://lists.mysql.com/plusplus?unsub=1
> > 
> > 
> 
> Nicolas PERRIN
> 
> 
> -- 
> MySQL++ Mailing List
> For list archives: http://lists.mysql.com/plusplus
> To unsubscribe:    http://lists.mysql.com/plusplus?unsub=1
> 
> 

Nicolas PERRIN

Thread
Re : Re: VS 2003 / Mysql++ 1.7(or 2.0 b) =&amp;gt;__int64 followed by 'long'is illegal ???np18 Jul
  • Re: Re : Re: VS 2003 / Mysql++ 1.7(or 2.0 b) =&amp;gt;__int64 followedby 'long'is illegal ???Warren Young18 Jul
    • Re: Re : Re: VS 2003 / Mysql++ 1.7(or 2.0 b) =&amp;gt;__int64 followedby 'long'is illegal ???Earl Miles18 Jul
      • Re: Re : Re: VS 2003 / Mysql++ 1.7(or 2.0 b) =&amp;gt;__int64 followedby 'long'is illegal ???Warren Young18 Jul
        • Re: Re : Re: VS 2003 / Mysql++ 1.7(or 2.0 b) =&amp;gt;__int64 followedby 'long'is illegal ???Warren Young18 Jul
        • Re: Re : Re: VS 2003 / Mysql++ 1.7(or 2.0 b) =&amp;gt;__int64 followedby 'long'is illegal ???Earl Miles18 Jul
          • Re: Re : Re: VS 2003 / Mysql++ 1.7(or 2.0 b) =&amp;gt;__int64 followedby 'long'is illegal ???Warren Young18 Jul
            • Re: Re : Re: VS 2003 / Mysql++ 1.7(or 2.0 b) =&amp;gt;__int64 followedby 'long'is illegal ???Earl Miles18 Jul
              • Re: reply-to discussionChris Frey21 Jul
                • Re: reply-to discussionEarl Miles21 Jul