Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61422
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5006EA43.608@sugarcrm.com>
References: <CAN+gjSe7r2SoRNYufcaB2ktK05shH1AcAsaFSbUibF9r4TeRrw@mail.gmail.com>
	<op.whkdiodaidpuyk@damnation>
	<CAEZPtU5Rb9W8iydy2-hoYqGDSWqd9WCTUXh214O-uCc3nVNiVA@mail.gmail.com>
	<50059AF8.5050805@sugarcrm.com>
	<CAEZPtU4hQ5GjMZ2b6T5d1_dTp01r7_rg8613JZ_5AuBVc29B7w@mail.gmail.com>
	<5005CB58.2020601@sugarcrm.com>
	<CAEZPtU6as2QKQKfp6cCrW=Xjq9v3ZW1u+jbNJBT0DfDQoa8CdA@mail.gmail.com>
	<50066724.6050901@sugarcrm.com>
	<CAEZPtU6hK8rZFA+QLT4vPch+QdZ9r4FgBsJAVcpaBWW7VFA1ow@mail.gmail.com>
	<50067040.3090307@sugarcrm.com>
	<CAEZPtU5=HFC=enGgNCLssFziOxViw5ekPv1e6Ky093rxOP5ZhQ@mail.gmail.com>
	<CAN+gjSfonNonHSBv4=9=VdVgP=OfvRQvLbshT1rxcZ83vrozYw@mail.gmail.com>
	<5006E5BB.50906@sugarcrm.com>
	<CAN+gjSeLTRP=AcnLQy-8_BLaaq3yEGF8nmvdBRq+5B3HAq+PUg@mail.gmail.com>
	<5006EA43.608@sugarcrm.com>
Date: Wed, 18 Jul 2012 19:50:12 +0200
Message-ID: <CAH-PCH4xZJadE59R2QFm65TeYDRe-_U8WdqT4kJQvM6ZA44iOw@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Pierre Joye <pierre.php@gmail.com>, internals <internals@lists.php.net>, 
	Andrew Faulds <ajfweb@googlemail.com>
Content-Type: multipart/alternative; boundary=047d7b33d5be754ce604c51e4baa
Subject: Re: [PHP-DEV] Pseudo-objects (methods on arrays, strings, etc.)
From: tyra3l@gmail.com (Ferenc Kovacs)

--047d7b33d5be754ce604c51e4baa
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

2012.07.18. 18:55, "Stas Malyshev" <smalyshev@sugarcrm.com> ezt =C3=ADrta:
>
> Hi!
>
> > Er, sorry, accidental capslock. This IS a new API. That was an example.
> > I'm not saying just put -> everywhere, I'm saying we can keep array_*
> > and add a new set of -> functions which are well-designed, consistent,
etc.
>
> What "this"? So far I didn't see any single message discussing anything
> about any API. All I see is discussing how we should have -> syntax
> working on arrays and strings. IMO this is exactly the wrong place to
> start, if your goal is to improve the API (if your goal is to have
> "sexy" syntax, it's fine but then I do not see this goal as worthy). The
> right place to start would be the API.
>
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

Maybe we could introduce a new namespace for the new api instead of turning
the new api oop only (or using objects for groupping static stateless
functions into objects only to hint that they are working with the same
variable types).

Combining this with the previously mentioned lets turn namespaces to first
class citizens and allowing exporting whole namespaces to the current scope
would make it possible to make the new api available in the global scope if
needed.
Ofc this still would be a huge task to rethink/reshape our current api.

--047d7b33d5be754ce604c51e4baa--