Re: [sqlite] Sqlite 3.3.7 intel compiler warnings

Jay Sprenkle uttered: hidden variables might very well not be a problem, if it was done that way on purpose. It should never be done on purpose. It is obfuscation pure and simple. There is never a good reason to do this, other than perhaps hiding a global variable (and even that is not a go

Re: [sqlite] Sqlite 3.3.7 intel compiler warnings

I know. I checked them all and at least they are dangerous and probably not obvious. I think the one in os_win.c is really a bug unless the intention were to always return OK. - To unsubscribe, send email to [EMAIL PR

Re: [sqlite] Sqlite 3.3.7 intel compiler warnings

hidden variables might very well not be a problem, if it was done that way on purpose. On 8/30/06, Miguel Angel Latorre Díaz <[EMAIL PROTECTED]> wrote: I already filtered out all the "common" warnings but these: build.c(1969): remark #1599: declaration hides variable "v" (declared at line 1883)

[sqlite] Sqlite 3.3.7 intel compiler warnings

I already filtered out all the "common" warnings but these: build.c(1969): remark #1599: declaration hides variable "v" (declared at line 1883) Vdbe *v = sqlite3GetVdbe(pParse); ^ expr.c(1520): remark #1599: declaration hides variable "op" (declared at line 1489)