> On Tue, 31 Jan 2017 15:50:08 -0800 James K. Lowden <jklow...@schemamania.org> > wrote:
> Last year there was much rejoicing when Microsoft decided to bundle > SQLite with Windows. That leaves me with a new question: if SQLite > announced its intention to move to C11 in 2018, would that perhaps > influence Microsoft's timeline to update its compiler? No. Microsoft products require multiple versions of multiple Microsoft and third-party compilers to compile any of their products. They will simply add whatever is needed to their internal compilers suite and use that to build the winsqlite.dll for distribution with Windows. Windows does not use ICU and does not support the use of timezones, etc, so there is no need for them to update their compilers at all as they will never use anything but the most primitive of any feature available. That said, there is no problem with Visual Studio compiling the ICU module as it was -- it works just fine without error. Just that when set to pedantic mode it produces a higher level of messages, whether they be a true statement of fact or not. The only issue I've run into using a Microsoft compiler is that it does not handle in-block initialization and declarations -- they all have to be at the top of a function before the first "executable" statement. I believe that was a C language restriction back in the early 70's. Of course, Microsoft compilers are somewhat, shall we say, crappy, and the code generated is also of the same calibre. Not to mention that there is neither forwards nor backwards runtime compatibility so you need to have just about every version of the compiler ever produced by Microsoft to do anything useful (which is not required with other compilers). _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
