On Thu, Aug 31, 2017 at 11:01 PM, Simon Slavin <slav...@bigfraud.org> wrote: > > > On 1 Sep 2017, at 4:49am, J Decker <d3c...@gmail.com> wrote: > >> That and MinGW defines NULL as 0 if C++ and not void(*) > > Oh Gawd, the old C/C++ problem. > > Some compilers and IDEs, by default, compile ".c" files as if they are C++. > This leads to all sorts of weird behaviour including both compiler error > messages and programs which compile fine then misbehave while running. NULL > is one of the things C and C++ do differently. > > I’m not saying this is the problem here, merely that it deserves a mention.
If you're in any slightly modern compiler, always use nullptr instead of NULL. -- Cory Nelson http://int64.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
