| Newsgroups |
gmane.mail.blat |
| Message-ID |
<[email protected]> |
Hi
Thank you for your reply. As I said I compile with visual studio 2015 because I had compiling problems with VS2012 Xp toolkit. I am using Xp toolkit because compiling under Unicode and without Xp toolkit simply, blat does not run under windows Xp.
> On 26 Ιουν 2016, at 7:53, "'Chip' [email protected] [blat]" <[email protected]> wrote:
>
> > Yes, that's what I did already :-)
> >
> > Anyway I had difficult time to compile BLAT using VS2012 and using XP toolkit (project Properties -> Configuration Properties -> Linker -> System -> SubSystem).
> >
> > As I read in the MS tech support they know the bug that the specific compiler and below (I think is version 11), does not support definitions string lengths bigger then 32 chars in the Resource files. If you look inside blat resource file, there is an TCHAR include, that have such definitions.
> >
> >
> > Anyway I tried to recompile using Visual Studio 2015 (ver 14) with XP 14 toolkit. The problem I had is an exception error when I declare some buf variables like this
> >
> > buf mailserver(_T("mail.xyz.com");
> > buf
> > buf
> > ...
> > ..
> >
> > and this happened only in release mode and not in a specific declaration. Anyone does have ever meet such kind of problems under Visual Studio 2015 and XP toolkit ? I am not sure but without XP toolkit it works just fine. I debugged the code and raised an exception in file management (If I remember well it was about sharing permissions...)
> >
> > PS:I am not in the office right now to copy/paste the offended code, but if you ask it for, i will do it to replicate the problem.
> >
>
> > buf mailserver(_T("mail.xyz.com");
>
> This above statement says that you have function called mailserver() that takes one string argument, and returns a buf class. I expect what you wanted is:
>
> Buf mailserver;
>
> mailserver = _T("mail.xyz.com");
>
> This does two things. The first statement declares the variable and calls the Buf class constructor to initialize the variable. The next statement then sets the variable’s array to the string.
>
> When compiling for Release mode, the compiler takes some liberties with variable declarations and initialization, while the Debug mode does not.
>
> I do not have the XP toolkit available with my Visual Studio 2010 installation. Therefore, I am not able to test what you are. However, I am curious what you are trying to accomplish that cannot be done simply by compiling for 32-bit with Unicode enabled?
>
> Chip
>