Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:53747 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 26277 invoked from network); 5 Jul 2011 16:02:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jul 2011 16:02:15 -0000 Authentication-Results: pb1.pair.com header.from=felipensp@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=felipensp@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.42 as permitted sender) X-PHP-List-Original-Sender: felipensp@gmail.com X-Host-Fingerprint: 209.85.210.42 mail-pz0-f42.google.com Received: from [209.85.210.42] ([209.85.210.42:57223] helo=mail-pz0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 69/E5-18802-685331E4 for ; Tue, 05 Jul 2011 12:02:15 -0400 Received: by pzk37 with SMTP id 37so2152063pzk.29 for ; Tue, 05 Jul 2011 09:02:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=j3NtYsOdEB1kq2b1wXWEu5a/9J0gzOLa4qDEEPu/Guc=; b=LmNJTxyW8a5oH4hCpQKyCZE+lgEP3QhyG4Ycx3E+ZhatA6O0IdqzX61PuedjZaEtZY rEe2XpZyyRawIHl/k7jCUDaKhZmAU1msIvfYzcrV3IcSaMEWD6kk9hkt4eyB5stcks5U wqhdvnneOBqa57HgCVz5bGLFog4wru8drn9gs= Received: by 10.142.240.5 with SMTP id n5mr160381wfh.221.1309881732110; Tue, 05 Jul 2011 09:02:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.142.222.7 with HTTP; Tue, 5 Jul 2011 09:01:52 -0700 (PDT) In-Reply-To: References: Date: Tue, 5 Jul 2011 13:01:52 -0300 Message-ID: To: Adam Harvey Cc: PHP internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [RFC] -W option for CLI "strict mode" From: felipensp@gmail.com (Felipe Pena) Hi, 2011/7/5 Adam Harvey : > Developers, Romans, countrymen, > > I'd like to propose the addition of a -W switch to the CLI SAPI which > would enable the display of errors and maximum error reporting. This > brings us into line with other languages such as Perl, and allows us > to evangelise to users that they should run "php -W script.php" as the > preferred way of developing and running new, E_STRICT-compliant > scripts. > > The RFC is at https://wiki.php.net/rfc/cli-strict, and comes with a > patch, which is accessible at > http://www.adamharvey.name/patches/php-cli-strict.patch.txt. If the > response isn't overwhelmingly negative and we don't get caught up in > discussions for the next few days, I'll look at calling for a vote in > a week or so (given it's not a language-level change). > > Thanks, > > Adam > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > Just to inform, the Perl's -W enable all warnings regardless of whether the script disable warnings. The Perl's -w one looks like your -W, but I know we already have used -w in PHP to output source with stripped comments and whitespaces. However I guess it's more useful to have something like Perl does with -W. -- Regards, Felipe Pena