Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:20023
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=j4jutFPKVloHJd7pX0HfdKLMK+rWDyRLf2EM2C+N6VQNnPXjaMKRLoZ6Qsen1xhEc+S+pJOfD13FS6ufgsdNkJOdbWcRx5KzlRVCab/x406AMU4hnfTqAcCweo64j0j1MN+n8MPI43dX69JeZ8r1Q2oh6+hNB8yHmujpEQDOwW0=
Message-ID: <4e89b4260511150942g6f3cab3boad1c09eb1c1e7318@mail.gmail.com>
Date: Tue, 15 Nov 2005 12:42:37 -0500
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Jani Taskinen <sniper@iki.fi>, internals@lists.php.net
In-Reply-To: <437A1BD1.9030309@lerdorf.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <437A0D24.6030701@caedmon.net>
	<Pine.LNX.4.61.0511151858240.25831@arfg.argcubovn.sv>
	<20051115181307.18c2b27b@localhost.localdomain>
	<437A1820.8060902@lerdorf.com>
	<Pine.LNX.4.61.0511151925260.25831@arfg.argcubovn.sv>
	<437A1BD1.9030309@lerdorf.com>
Subject: Re: [PHP-DEV] date() behaviour changed in 5.1?
From: kingwez@gmail.com (Wez Furlong)

I can't think of any case where you'd want to error out when given
'100 ' if it would accept '100' quite happily.

I'd lean towards a single cast semantic for this, and remove that
strict checking flag from zend_parse_parameters(); lazy dynamic type
handling for primitive data types is one of the cornerstones of PHP
IMO.

--Wez.


On 11/15/05, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:
> Jani Taskinen wrote:
> > On Tue, 15 Nov 2005, Rasmus Lerdorf wrote:
> >
> >>
> >> Pierre wrote:
> >>> On Tue, 15 Nov 2005 18:59:32 +0200 (EET)
> >>> sniper@iki.fi (Jani Taskinen) wrote:
> >>>
> >>>>      If you pass bad data to a function, it should not warn you?
> >>>>      I'd rather have it as a FATAL error. :)
> >>>>
> >>>>      Nothing to fix here, move along. (and fix your code..)
> >>>
> >>> PHP is losely typed, I see nothing wrong to pass an integer as string
> >>> there (for example, imagecreate("100", "100"); works).
> >>
> >> The question isn't what to do with "100","100" but what to do with
> >> "100abc","100abc".  Should that still work?  The old
> >> zend_get_parameters() following by a convert_to_long() says Yes.  The
> >> newer zend_parse_parameters() says no.
> >
> >     With new version it's possible to catch such typos, with old one th=
ey'd
> >     just be silently ignored and perhaps could cause very hard to find
> > bugs in your code..
>
> I suppose, but I still find it weird that:
>
>    date("h", (int)$foo);
>
> and
>
>    date("h", $foo);
>
> will behave differently when $foo isn't a clean numeric string.  And
> when we move 100% to zend_parse_parameters() in PHP 6 there will be many
> more functions changing their behaviour due to this.
>
> -Rasmus
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>