I put the amalgamated 3.22.0 release into my production code. Windows 10 is
the customer execution platform. Do I need to update?
___
Mark C Edwards
Chief Scientist, C2 Systems Engineering & Integration
779 Monika Ct
Chubbuck, ID 83202
mark.c.edwa...@leidos
Release mode/x86 Visual Studio 2015 Prono problems with the new snapshot
___
Mark C Edwards
Chief Scientist, C2 Systems Engineering & Integration
779 Monika Ct
Chubbuck, ID 83202
mark.c.edwa...@leidos.com
Mobile: 208-241-7982
-Original Message-
The Release build/X86 on Visual Studio 2015 Pro worked. The prior problem with
"possible uninitialized variables" has been resolved. 3.22.0 looks like a
viable candidate
for incorporation in our source base. We use only the amalgamated sqlite3.h,
sqlite3ext.h and sqlite3.c files.
Thanks!
_
Thanks Richard. I'll build the amalgamated version in Release mode/X86 in VS
2015 Pro to see if it completes without complaint.
___
Mark C Edwards
Chief Scientist, C2 Systems Engineering & Integration
779 Monika Ct
Chubbuck, ID 83202
mark.c.edwa...@leidos.co
12/15/17, Edwards, Mark C. wrote:
> sqlite3.c(167291): error C4703: potentially uninitialized local
> pointer variable 'pNode' used
> sqlite3.c(168154): error C4703: potentially uninitialized local
> pointer variable 'pRoot' used
> sqlite3.c(168160): error C4703
sqlite3.c(167291): error C4703: potentially uninitialized local pointer
variable 'pNode' used
sqlite3.c(168154): error C4703: potentially uninitialized local pointer
variable 'pRoot' used
sqlite3.c(168160): error C4703: potentially uninitialized local pointer
variable 'pChild' used
Two of these
6 matches
Mail list logo