Simon,
On Sun, Jun 26, 2016 at 12:16 AM, Igor Korot wrote:
> Simon,
>
> On Sat, Jun 25, 2016 at 11:31 PM, Simon Slavin wrote:
>>
>> On 26 Jun 2016, at 3:30am, Igor Korot wrote:
>>
>>> ATM I'm using OSX 10.8 with Xcode 5.1.1. compiling everything for C++11
>>> and libc++.
>>
>> You should not be
Mr. Hipp,
On Sat, Jun 25, 2016 at 11:31 PM, Richard Hipp wrote:
> On Sun, Jun 26, 2016 at 4:30 AM, Igor Korot wrote:
>>
>> I am wondering what is the current policy on the compilation
>> warning for the SQLite?
>>
>
> In short, the policy of SQLite towards warnings is "Don't Panic!".
That's a g
Simon,
On Sat, Jun 25, 2016 at 11:31 PM, Simon Slavin wrote:
>
> On 26 Jun 2016, at 3:30am, Igor Korot wrote:
>
>> ATM I'm using OSX 10.8 with Xcode 5.1.1. compiling everything for C++11
>> and libc++.
>
> You should not be getting numerous warnings. One or two, maybe.
>
> Make sure that Xcode
On 26 Jun 2016, at 3:30am, Igor Korot wrote:
> ATM I'm using OSX 10.8 with Xcode 5.1.1. compiling everything for C++11
> and libc++.
You should not be getting numerous warnings. One or two, maybe.
Make sure that Xcode knows that your .c file is C and not C++. This is a big
problem with Xcod
On Sun, Jun 26, 2016 at 4:30 AM, Igor Korot wrote:
>
> I am wondering what is the current policy on the compilation
> warning for the SQLite?
>
In short, the policy of SQLite towards warnings is "Don't Panic!".
A "bug" means that the software computes an incorrect answer.
Compiler warnings are n
Hi, ALL,
I am wondering what is the current policy on the compilation
warning for the SQLite?
The reason being - I'm trying to incorporate SQLite into my software.
The software will be cross-platform.
On both Windows and Linux, I don't see any issues.
However, trying to compile on Mac I have a lo
6 matches
Mail list logo
