Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:51779
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=RaWSyjri9aa3bmlCR4C08HAKCK+kuO8svmINhEVGiTWtGU1RM05CHdfYszhlJymtqL
         gbz1PENYgbeg3u0kJgC3KdAksPCm8HGRl7fPYUpVGC2QpMSdHqgaQ8bhxPly3Ik6FDkK
         2GjXyXlNevgGZ9cV/c+gsuKINRYmfDvlkum58=
MIME-Version: 1.0
In-Reply-To: <4D94C380.2070402@lerdorf.com>
References: <AANLkTinWgyueX7FJKdHASzOV0X0L480jnjd=o=mrG2kZ@mail.gmail.com>
	<4D92CC38.5040900@toolpark.com>
	<AANLkTimpmjOQcqLcfH23Zrt6EULw6PAJvQ1_cvAP7ON=@mail.gmail.com>
	<AANLkTinp1wnOu6te6MjoONcz_1AVobc7pwFwvbY8mkTB@mail.gmail.com>
	<004301cbeee8$e54a8280$afdf8780$@com>
	<AANLkTi=MTU=AM-FeX1ZbTrrEDdNCPWNvcppWrxxbWGcg@mail.gmail.com>
	<4D9387BE.4030808@divbyzero.net>
	<E6786318-197A-4C8A-AAE2-A24DADDA7BA2@roshambo.org>
	<4D94984D.8060700@lerdorf.com>
	<AANLkTi=j1z8f8bO10Z9yENEN9NTPkt3Y7nBPDngkSLFi@mail.gmail.com>
	<4D94A111.7050501@moonspot.net>
	<520FB834-2614-4873-AC3B-0B2594B18471@roshambo.org>
	<4D94A350.70201@lerdorf.com>
	<AANLkTinnvOy+gh-ZfJqf3SND3qFZ8ecntThfu2Yfo5Bm@mail.gmail.com>
	<4D94C380.2070402@lerdorf.com>
Date: Thu, 31 Mar 2011 11:40:21 -0700
Message-ID: <AANLkTinPnMNP=EfEjaMdfTH47QOvu9wpVVH16kYHS1dm@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Martin Scotta <martinscotta@gmail.com>, internals@lists.php.net
Content-Type: multipart/alternative; boundary=bcaec50162c52daad4049fcba043
Subject: Re: [PHP-DEV] Adding a more logical string slicing function to PHP
From: birken@gmail.com (Dan Birken)

--bcaec50162c52daad4049fcba043
Content-Type: text/plain; charset=ISO-8859-1

On a somewhat related note (and going back a little to my original patch),
languages like python and ruby allow slicing on array/string objects with
$string_or_array[start:end] syntax.  I think this would be really useful
syntax in PHP as well (and would of course make the initial patch I
submitted obsolete).  The one thing I was hesitant about with my patch was
polluting the global function space for PHP, and I think adding new and
specific syntax to provide these things is much better.

I have no idea how feasible it is given PHP's internal structure, but if it
was possible I would be glad to try to write a patch for it.

-Dan

On Thu, Mar 31, 2011 at 11:10 AM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:

> On 03/31/2011 10:58 AM, Martin Scotta wrote:
> > I think it's time to stop thinking in terms of "functions" and move
> > forward to "abstractions"
> >
> > $s1 = 'string';
> > $s1->contains($s2);
> >
> > $s1->indexOf($s2) === strpos($s1, $s2);
> >
> > Why can't the strings be exposed as pseudo-objects ? users can choose to
> > use them as a regular strings or by calling methods on it.
>
> This is actually something I have been toying with a bit. Adding the
> ability to call methods on both strings and arrays. I still don't like
> the idea of making them real objects as the overhead and the amount of
> code that would need to be changed in the core and in every extension is
> daunting. Anybody out there have a patch along these lines?
>
> -Rasmus
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--bcaec50162c52daad4049fcba043--