Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:21720
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:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=eM90F8EVo9Ep5DeVc/kXllKKAaSJOhYdx4ZvblvlXOpoHf3XjF+HaB5z65lH2glkY3tAYSjbrBrTLW+iIkUBaL7Ys+l8xDldp2gdie4YoDUBFRlG1Ab2ysDs36JDmfV0zSv88yJTCgr5rrY4RE/A+KE3aa3a3eoIr3ckxWHufjw=
Message-ID: <2a8d4a710601291221q186165adwe780ca5f3ee253@mail.gmail.com>
Date: Sun, 29 Jan 2006 15:21:20 -0500
To: php internals <internals@lists.php.net>
In-Reply-To: <2a8d4a710601291220i5d33202ewabe9337d40043299@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <2a8d4a710601282225g4f06a6c7v59edb232eb9584a4@mail.gmail.com>
	<43DC7227.4070600@dealnews.com>
	<23b513280601290844h1c58f798qba32ed20848f2da2@mail.gmail.com>
	<2a8d4a710601291032g3e4b3b93i3f3edc5b19c66dc8@mail.gmail.com>
	<23b513280601291046v24720f2bl28b0a88fadcc90be@mail.gmail.com>
	<2a8d4a710601291220i5d33202ewabe9337d40043299@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP Array Literals
From: chiology@gmail.com (James Crane)

Then why don't we have these:

$i =3D integer(5);
$f =3D float(4.5);
$s =3D string("foo");

And what about classes? It's slightly different, what with it being a
definition rather than a specific literal value, but it produces a
definition, pseudo value if you will, so why not have:

class("MyClass", array("method", array("arguments"), "method body here"));

Of course, that woudln't make sense. We, instead, use appropriate syntax:

class MyClass {
 public function method($arguments) {
   // method body here
 }
}

Suitable, logical, appropriate code. To me, 'array()' just seems on
the verge of being (but not totally) inappropriate.

M.T.