The problem seems to be with a #define followed by a opening curly brace,
also for example:
#define WRITE_UTF8(zOut, c) { \
at line 27227Could it be that VS needs some setting to recognize this construction? RBS On Tue, Feb 14, 2017 at 3:32 PM, Simon Slavin <slav...@bigfraud.org> wrote: > > On 14 Feb 2017, at 3:06pm, Bart Smissaert <bart.smissa...@gmail.com> > wrote: > > > Yes, didn't expect this was reproducible. > > All I can think of is that somehow MSVS doesn't recognize this now as C > > code. > > Must be one of the settings in VS that has somehow changed. > > Well, I’m not a C whiz, but that code looks like legal C. > > Is the VC compiler a C++ compiler ? I’ve seen problems before from > compilers which tried to compile SQLite source code files (.c files) as if > they were C++ files (.cpp files). The biggest problem here was that the > errors they indicated were at the 'wrong' place, sometimes even in the > 'wrong' files, because most C is legal C++. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
