Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:52384 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35632 invoked from network); 16 May 2011 09:43:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 May 2011 09:43:16 -0000 Authentication-Results: pb1.pair.com smtp.mail=rquadling@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rquadling@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.177 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: rquadling@gmail.com X-Host-Fingerprint: 209.85.216.177 mail-qy0-f177.google.com Received: from [209.85.216.177] ([209.85.216.177:41921] helo=mail-qy0-f177.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FC/71-26716-3B1F0DD4 for ; Mon, 16 May 2011 05:43:15 -0400 Received: by qyl38 with SMTP id 38so2805235qyl.8 for ; Mon, 16 May 2011 02:43:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=cKNt0o6hw4p13KOd+32X0eAOHRGAJ6MtNudgFWdsJ8w=; b=qc6luw7THM4IV7QlcqthyL2h0Zjzho3ppcHWfOlCSQ65RDcWvjZaEaCjrymXHvZYFz 0vjNHHLUZvhhu8XMBbwu5/h0Orjb33u2KMl3ilVJE16M5eMWVvN/tr84opO0R1Ho+A+j Fn54xOxXU83NELzkzOTgioJiMcD6tC6/viGB0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; b=vELODjaw+ZOaSOx/QnOSK7qizjr3iPx7peHI3Z3rb1VQBev+u499+eDVRy9fAQOmw3 W+EiFrbWPn+5/o3QPyZEJfb9gr7oSn/Ktpl/VefPsHRuTDybO0hYMwEjdpB4osrEuwFd QILWpug0/NykiG0jStYT10p+tQ3touL24JOKk= Received: by 10.229.13.152 with SMTP id c24mr3166493qca.87.1305538992310; Mon, 16 May 2011 02:43:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.85.137 with HTTP; Mon, 16 May 2011 02:42:52 -0700 (PDT) Reply-To: RQuadling@GMail.com In-Reply-To: References: <36.60.32666.EB930DD4@pb1.pair.com> Date: Mon, 16 May 2011 10:42:52 +0100 Message-ID: To: Pierre Joye Cc: internals@lists.php.net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [rmtools][php-5.4] Build error between r and 311062 From: rquadling@gmail.com (Richard Quadling) On 16 May 2011 00:44, Pierre Joye wrote: > hi, > > On Mon, May 16, 2011 at 12:11 AM, Richard Quadling = wrote: >> On 15 May 2011 21:37, =C2=A0 wrote: >>> >>> This is an automatic mail from the rmtoool's build bots. >>> >>> New build errors have been introduced between >>> and 311062. >>> >>> The errors are: >>> >>> php-5.4, build ts-windows-vc9-x86: >>> , NMAKE, error, U1077, '"C:\Program Files (x86)\Microsoft Visual Studio= 9.0\VC\BIN\cl.exe"' : return code '0x2', >>> >>> >>> >>> Full logs are available at (htmlized versions too): >>> >>> http://windows.php.net/downloads/snaps/php-5.4/r311062 >> >> With 3,475 warnings in the Win32 x86 VC9 nts build, how do you see the >> wood for the trees? > >> If the warnings can be ignored, why not suppress them? > > Ideally almost all could be suppressed. However there are many false > positive or cases that can't happen (theoretically). Keeping in mind > that this log is the static analyzer logs. Once I got the new machines > running, both normal and analyzers log will be published. > > The key then is to detect the delta between two revisions (should be > up soon) and then fix those already. > > That being said, a warning php has been a sweet from many of us but > some devs simply do not want that ;-). > > Cheers, > -- > Pierre > > @pierrejoye | http://blog.thepimp.net | http://www.libgd.org > "some devs simply do not want that" Why not? I'm guessing the amount of effort required to resolve false positives outweighs the benefit. When I was taught programming, compiler warnings were explained as the compiler telling me that I had not made my intent 100% crystal clear and that the compiler was making a good guess but possibly an incorrect or inappropriate one. Not a bug per se, but just an error in judgement. And when you are compiling across so many different systems, would it not be beneficial to at least re-examine some of these warnings. Just in case ...? Or am I just wasting my time and you all know exactly which warnings are just junk? Are you all that good? Richard. --=20 Richard Quadling Twitter : EE : Zend @RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY