On 29.09.2017 22:33, Scott Robison wrote:
> On Fri, Sep 29, 2017 at 1:20 PM, Bob Friesenhahn
> wrote:
>> > On Fri, 29 Sep 2017, Scott Robison wrote:
>>> >>
>>> >>
>>> >> The problem is that there is no one best practice for resolving all
>>> >> such warnings in a
Many thanks to Mr. J Decker. I'm glad if I've made anybody think about
that warnings. My mission is complete if it's true.
On 29.09.2017 21:58, J Decker wrote:
> On Fri, Sep 29, 2017 at 1:07 AM, Denis V. Razumovsky <t...@denis.im> wrote:
>
>> Please remove multiple warnings f
I am absolutely sure that sqlite is one of the best and the most tested
software product in the nature and having such a point of view I was
rather surprised at number of warnings coming from the compiler. I have
no plans to thrust my opinion on the community, just to draw attention
to the
l analyses with zero warnings.
You can see entire document here:
https://web.eecs.umich.edu/~imarkov/10rules.pdf
On 29.09.2017 19:28, Jens Alfke wrote:
>
>> On Sep 29, 2017, at 1:07 AM, Denis V. Razumovsky <t...@denis.im> wrote:
>>
>> Please remove multiple warnings from com
Please remove multiple warnings from compiler about optimisation,
variable conversion, signed overflow and many more potential errors.
1. Optimisation solutions from GCC:
If you would like to add extra warning attributes to compile SQLite with
gcc (and many others modern compilers) you will see
5 matches
Mail list logo