From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Fixed some compiler warnings |
Date: | 2014-01-31 13:56:45 |
Message-ID: | CA+OCxoy+-DRzvaWonUb6fwhbq2fM34qs3k4JGbjKp7pkJF8BxQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Fri, Jan 31, 2014 at 6:03 AM, Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com
> wrote:
>
>
>
> On Thu, Jan 30, 2014 at 7:35 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>
>> Hi
>>
>>
>> On Thu, Jan 30, 2014 at 9:35 AM, Akshay Joshi <
>> akshay(dot)joshi(at)enterprisedb(dot)com> wrote:
>>
>>> Hi Dave
>>>
>>> I have fixed some compiler warnings which we are facing on OSXMavericks. Attached
>>> is the patch file. Can you please review it.
>>>
>>> If patch looks good to you then can you please commit it.
>>>
>>>
>> It mostly looks good, but what's with the operator changes? Why is it
>> complaining about x >= 0 ?
>>
>
> In all such cases x is unsigned int and compiler complaining about
> condition "x >=0" will always true.
>
Ahh yes. However, the proposed fix will always evaluate to true won't it?
if (i > 0 || i == 0)
{
}
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Shane StClair | 2014-01-31 22:17:20 | Format SQL (external tool) |
Previous Message | Akshay Joshi | 2014-01-31 06:03:12 | Re: Fixed some compiler warnings |