Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On 3 Feb 2017, at 4:24pm, Warren Young wrote: > On Feb 3, 2017, at 9:15 AM, Simon Slavin wrote: > >> My solicitors will be in the post. > > How much does it cost to mail a lawyer where you are? Do they charge by > weight or unusual shape? Oh, the

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On Feb 3, 2017, at 9:15 AM, Simon Slavin wrote: > > My solicitors will be in the post. How much does it cost to mail a lawyer where you are? Do they charge by weight or unusual shape? ___ sqlite-users mailing list

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On 3 Feb 2017, at 2:35pm, James K. Lowden wrote: > When I was > using Microsoft's C++ intensively, I would find a compiler bug about > once a month. A different set of bugs depending on the optimization level you were using. Oh man, you brought it all back. My

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On Wed, 01 Feb 2017 17:48:48 -0500 "Keith Medcalf" wrote: > 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

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On Wed, Feb 1, 2017 at 3:48 PM, Keith Medcalf wrote: > > > 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

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

> On Tue, 31 Jan 2017 15:50:08 -0800 James K. Lowden > 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

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of James K. Lowden >>>Despite the fact that the Windows API is defined in terms of C, Microsoft >>>evidently and probably correctly has decided its market does not demand a >>>modern C compiler. The Microsoft

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On Jan 31, 2017 6:25 PM, "James K. Lowden" wrote: On Tue, 31 Jan 2017 15:50:08 -0800 Nathan Bossett wrote: > Since this is the sqlite users list and not the dev's list, can I ask > what your use case is that writing a thin wrapper around SQLITE >

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On Tue, 31 Jan 2017 15:50:08 -0800 Nathan Bossett wrote: > Since this is the sqlite users list and not the dev's list, can I ask > what your use case is that writing a thin wrapper around SQLITE > doesn't solve your problem? I've encountered no problem compiling SQLite

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On Tue, Jan 31, 2017 at 11:48:10AM -0500, James K. Lowden wrote: > On Mon, 30 Jan 2017 13:32:46 -0700 > Scott Robison wrote: > > > Basing source on "ANSI C" (as much as possible) just gives you the > > biggest possible distribution / compatibility. > > Yes, but it also

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On Tue, Jan 31, 2017 at 9:48 AM, James K. Lowden wrote: > On Mon, 30 Jan 2017 13:32:46 -0700 > Scott Robison wrote: > > > Basing source on "ANSI C" (as much as possible) just gives you the > > biggest possible distribution / compatibility. > >

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On Mon, 30 Jan 2017 13:32:46 -0700 Scott Robison wrote: > Basing source on "ANSI C" (as much as possible) just gives you the > biggest possible distribution / compatibility. Yes, but it also limits you to C as it stood 20 years ago. And counting. Is there no point at

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

It's an iBook, so some version of OS X I would guess. From a little searching online, 10.2 was the last release in 2002, and it seems that it may have included GCC 3.3. GCC 3.3 did not fully support C99 (as its release notes indicated "A few more ISO C99 features now work correctly." Of course,

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On Sun, 29 Jan 2017 21:40:23 -0500 Richard Hipp wrote: > On 1/29/17, James K. Lowden wrote: > > > > I wonder what pricey embedded environment both supports dlopen(2) > > and does not support C99, in this day and age. > > One of the test platforms for

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of Hick Gunter >>>Integer promotion is usually ok between integers of the same signedness. For some definition of 'OK'. >>>However, in unsigned char uns = 0xff; long val = uns; >>>what should be

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

>-Ursprüngliche Nachricht- >Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im >Auftrag von James K. Lowden >Gesendet: Freitag, 27. Jänner 2017 20:08 >An: sqlite-users@mailinglists.sqlite.org >Betreff: Re: [sqlite] BUG: Illegal initi

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On 1/29/17, James K. Lowden wrote: > > I wonder what pricey embedded environment both supports dlopen(2) and > does not support C99, in this day and age. > One of the test platforms for SQLite is an old iBook I bought back in approximately 2002. Dunno if it support C99

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On Sunday, 29 January, 2017 19:50, Simon Slavin , said: > On 30 Jan 2017, at 12:06am, Scott Robison wrote: > > I'm not sure how big the market is, but there are older computers in use > > in areas that might be running older OS because anything

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On Jan 29, 2017 5:49 PM, "Simon Slavin" wrote: On 30 Jan 2017, at 12:06am, Scott Robison wrote: > I'm not sure how big the market is, but there are older computers in use in > areas that might be running older OS because anything newer is too

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On 30 Jan 2017, at 12:06am, Scott Robison wrote: > I'm not sure how big the market is, but there are older computers in use in > areas that might be running older OS because anything newer is too bloated. The emphasis is shifted to non-modern compilers because a large

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

I'm not sure how big the market is, but there are older computers in use in areas that might be running older OS because anything newer is too bloated. If maintaining ANSI C compatibility truly becomes a burden, sure. If it isn't then why not? On Jan 29, 2017 4:36 PM, "James K. Lowden"

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On Sat, 28 Jan 2017 11:49:19 +1100 "dandl" wrote: > >>>Sticking with C90 is perfectly rational if you're still running > >>>Windows 98 on a Pentium III at 500 Mhz with 256 MB RAM. Else, > >>>really, it's not too soon to adopt a 6-year old standard, C11. > > There are plenty

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On Fri, Jan 27, 2017 at 7:49 PM, dandl wrote: > From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] > On Behalf Of James K. Lowden > > >>>Sticking with C90 is perfectly rational if you're still running Windows > 98 on a Pentium III at 500 Mhz with 256 MB

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of James K. Lowden >>>Sticking with C90 is perfectly rational if you're still running Windows 98 >>>on a Pentium III at 500 Mhz with 256 MB RAM. Else, really, it's not too >>>soon to adopt a 6-year old

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On 1/27/17 6:06 PM, Keith Medcalf wrote: On Friday, 27 January, 2017 08:26, Clemens Ladisch said: David Empson wrote: Perhaps SQLite’s test procedure should be enforcing strict ANSI C mode? If this is already being done, then the compiler(s) used might not be enforcing

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On Friday, 27 January, 2017 08:26, Clemens Ladisch said: > David Empson wrote: > > Perhaps SQLite’s test procedure should be enforcing strict ANSI C mode? > > If this is already being done, then the compiler(s) used might not be > > enforcing this particular rule. > > "gcc

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On Fri, 27 Jan 2017 10:08:17 +1300 David Empson wrote: > Should SQLite be aiming for the 1990 version of ANSI/ISO C as a > baseline, for widest compatibility, or is it OK to drop older > compilers and require C99 compliance? Older compilers? C99 was adopted 17 years ago,

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On Thu, 26 Jan 2017 08:19:02 + Hick Gunter wrote: > On LP_64 architactures, the integer 0 is 32 bits while (void *)0 is > 64 bits, which makes more than a bit of a difference. A 64 bit > integer 0 would be denoted by 0L. in C, as you know, integer assignment is subject to

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

I wrote: > David Empson wrote: >> Perhaps SQLite’s test procedure should be enforcing strict ANSI C mode? >> If this is already being done, then the compiler(s) used might not be >> enforcing this particular rule. > > "gcc -pedantic -std=c90" (or gnu90) would check for this error And

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

David, On Fri, Jan 27, 2017 at 12:51 PM, David Empson wrote: > >> On 27/01/2017, at 9:09 PM, Kim Gräsman wrote: >> >> On Thu, Jan 26, 2017 at 10:08 PM, David Empson > > wrote: >>> On

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

David Empson wrote: > Perhaps SQLite’s test procedure should be enforcing strict ANSI C mode? > If this is already being done, then the compiler(s) used might not be > enforcing this particular rule. "gcc -pedantic -std=c90" (or gnu90) would check for this error: test.c:6:3: warning: initializer

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

> On 27/01/2017, at 9:09 PM, Kim Gräsman wrote: > > On Thu, Jan 26, 2017 at 10:08 PM, David Empson > wrote: >> >>> On 26/01/2017, at 8:46 PM, Clemens Ladisch wrote: >>> …

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On Thu, Jan 26, 2017 at 10:08 PM, David Empson wrote: > >> On 26/01/2017, at 8:46 PM, Clemens Ladisch wrote: >> >> Ziemowit Laski wrote: >>> Visual C++ >> >> Which one? >> >>> correctly catches this. >> >> Oh? What exactly is illegal about this? >> >>>

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On Fri, Jan 27, 2017 at 1:24 AM, Richard Hipp wrote: > On 1/26/17, dandl wrote: > > > > 1. Why was VS the first compiler to detect this? > > Perhaps VS is the only compiler still in frequent use that does not > support C99? I guess David's question can also be

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On 1/26/17, dandl wrote: > > 1. Why was VS the first compiler to detect this? Perhaps VS is the only compiler still in frequent use that does not support C99? > 2. Is there an authoritative view on which standard Sqlite should comply > with? > SQLite should compile with VS. I

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On Behalf Of David Empson >>>The ANSI/ISO C 1990 standard states this in section 6.5.7, under Constraints: >>>“All the expressions in an initializer for an object that has static storage >>>duration or in an initializer

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

> On 26/01/2017, at 8:46 PM, Clemens Ladisch wrote: > > Ziemowit Laski wrote: >> Visual C++ > > Which one? > >> correctly catches this. > > Oh? What exactly is illegal about this? > >> struct IcuScalar { >>const char *zName;/* Function name

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

On 1/26/17 8:05 AM, Hick Gunter wrote: The OP proposes intializing the structure member with "0" instead of "(void*)db", which I read the other way around and reminds me of certain implicit equivalences 0 <==> (void*)0, on eof which was recently discussed here. Perhaps the OP's Compiler does

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

>>>From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On >>>Behalf Of Ziemowit Laski Sent: Thursday, 26 January 2017 7:36 AM To: sqlite-users@mailinglists.sqlite.org Subject: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit >>> >

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

nitialization of a dynamic structure with a parameter value. -Ursprüngliche Nachricht- Von: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] Im Auftrag von Clemens Ladisch Gesendet: Donnerstag, 26. Jänner 2017 13:07 An: sqlite-users@mailinglists.sqlite.org Betreff:

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

Hick Gunter wrote: > On ILP_32 architectures, the integer 0 What integer 0? The message is about initializing scalars[11].pContent (a "void*") with "(void*)db", which is "sqlite3*". > Oh? What exactly is illegal about this? > >> struct IcuScalar { >> const char *zName;

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

Auftrag von Clemens Ladisch Gesendet: Donnerstag, 26. Jänner 2017 08:47 An: sqlite-users@mailinglists.sqlite.org Betreff: Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit Ziemowit Laski wrote: > Visual C++ Which one? > correctly catches this. Oh? What exactly is ille

Re: [sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

Ziemowit Laski wrote: > Visual C++ Which one? > correctly catches this. Oh? What exactly is illegal about this? > struct IcuScalar { > const char *zName;/* Function name */ > int nArg; /* Number of arguments */ > int enc;

[sqlite] BUG: Illegal initialization in icu.c : sqlite3IcuInit

Visual C++ correctly catches this. The fragment struct IcuScalar { const char *zName;/* Function name */ int nArg; /* Number of arguments */ int enc; /* Optimal text encoding */ void