Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58228
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.170 as permitted sender)
Received-SPF: pass (google.com: domain of kris.craig@gmail.com designates 10.180.24.4 as permitted sender) client-ip=10.180.24.4;
MIME-Version: 1.0
In-Reply-To: <A633CF2D7C7BED41B41F1E64F25507B8069DC46C55@MAILR001.mail.lan>
References: <CAG=uTXEfTBqX7n0_zfGjB_txQFKtZXF4MOo6RHHPSRPerGeKZA@mail.gmail.com>
	<CAKOpQSwP_VXazO1WgQgOWiKTmgiwzorg2=ii+Mdz58a=TKs6VA@mail.gmail.com>
	<CAGovj_O5UQx9aAaYg302i-kKp13CtBKNLmQ48OLHNvk61rM1sw@mail.gmail.com>
	<1330357150.2159.30.camel@guybrush>
	<CAGovj_MUt60EJfG8a7r-cqrC2PKsi8mqh6v_iyNoRDq8q-jh2Q@mail.gmail.com>
	<CAH-PCH6Bre5yzc6r3zxEj3=zZY0PHDOCVQ0s=f8JBDSPnK+5Fw@mail.gmail.com>
	<CAAyV7nFmfhb97CGAK1ZAkp9qb3oCPxbUDnS-Z-v3cP2APcYs=g@mail.gmail.com>
	<CAH-PCH5mYpAJAyMoyODDSwTvmgpf6ZN_dmC58v0b=K-s-mL0EA@mail.gmail.com>
	<CAAyV7nEpCWE2Gg5MCvfyhGGspgMGB+oYORKK=BKfm48sgXkROA@mail.gmail.com>
	<4F4C1324.2040905@gmail.com>
	<CAKOpQSzop8NuwnD1gPYmgzE2=E5_AHj_N+-ezTp4DFpHXktTqw@mail.gmail.com>
	<A633CF2D7C7BED41B41F1E64F25507B8069DC46C55@MAILR001.mail.lan>
Date: Mon, 27 Feb 2012 20:57:48 -0800
Message-ID: <CAKOpQSyptTG2=+QtxZoDAB9uh=T=Jgw0DzsAEpTSPv5fGLY7mw@mail.gmail.com>
To: John Crenshaw <johncrenshaw@priacta.com>
Cc: =?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?= <keisial@gmail.com>, 
	Anthony Ferrara <ircmaxell@gmail.com>, Ferenc Kovacs <tyra3l@gmail.com>, 
	Michael Morris <dmgx.michael@gmail.com>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d043be1c684c6dc04b9ff116b
Subject: Re: [PHP-DEV] Scalar type hinting
From: kris.craig@gmail.com (Kris Craig)

--f46d043be1c684c6dc04b9ff116b
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Lol you're making me feel like an old fogey!  I've always just used
email/listservs (or carrier pigeon if I'm getting a busy signal dialing in
to AOL).

Either way, I think we should give serious thought to how we move forward
on this, as it could wind up being a blueprint for future PHP feature
collaborations.  I do agree with all your points though.  Let me ponder
over it a little bit then get back to ya, just in case I have a better idea
that I haven't thought of yet.  ;)

--Kris


2012/2/27 John Crenshaw <johncrenshaw@priacta.com>

> I don't think we need yet another list. That said, I think that some
> features (such as weak typing) would benefit greatly from having a small
> body of people get together and flesh out a proposal together before
> presenting it for sacrifice on the altar of public discussion. Part of th=
e
> value in this is keeping the group limited to just collaborators on that
> specific feature, so a general features mailing list wouldn't really add
> anything.
>
> Not sure how you want to coordinate this group. In my company we have a
> distributed team and we typically coordinate this sort of design process
> using Google Docs + Donedesk(our own product, but free) + Skype. This wor=
ks
> well and strikes a nice balance between persistent and realtime
> collaboration. I'm open to other ideas, but if I had to choose how to
> coordinate a group to design a single feature, that's what I would use.
>
> John Crenshaw
> Priacta, Inc.
>
> -----Original Message-----
> From: Kris Craig [mailto:kris.craig@gmail.com]
> Sent: Monday, February 27, 2012 6:36 PM
> To: =C1ngel Gonz=E1lez
> Cc: Anthony Ferrara; Ferenc Kovacs; Michael Morris;
> internals@lists.php.net
> Subject: Re: [PHP-DEV] Scalar type hinting
>
> I agree.  What does everyone think about the idea of creating a new list
> specifically discussion of new feature ideas?  The idea could be announce=
d
> on the Internals list with a link to the discussion on the other list.
> That way, the noise ratio would be reduced and only those who are
> interested in brainstorming new ideas would have to listen to it.
>
> Thoughts?
>
> --Kris
>
>
> 2012/2/27 =C1ngel Gonz=E1lez <keisial@gmail.com>
>
> > On 27/02/12 22:52, Anthony Ferrara wrote:
> > > Ferenc,
> > >
> > > Thanks for the comments!
> > Thanks from me, too.
> >
> > And thanks to you, Anthony if you get to summarise that.
> >
> >
> > >> There were ideas, but they didn't have enough traction.
> > >> IMO we can't have a proper solution without changing the existing
> > behavior
> > >> for complex types, if you implement strict typing for scalars that
> > turns the
> > >> language strict typed, if you add dynamic/weak typing for the
> > >> scalars,
> > you
> > >> will have an inconsistent implementation.
> > > What behavior would need to be changed for complex types?  Adding
> > > the ability to hint/cast between trees?  I'm kind of confused by
> > > this bit...
> > I suspect one of the scalars should be complex (=3D objects?)
> >
> >
> >
> > > I think that's my biggest problem with the dynamics of this list.
> > > Ideas aren't really nurtured as well as they could be.  If the idea
> > > is solid, and has an implementation, then it's great.  But there are
> > > plenty of seedling ideas that get lost or down trodden-ed simply
> > > because it's not bulletproof...
> > Yes, the noise ratio of this list is quite high. Probably related to
> > its high volume. That makes people faster in discarding ideas as "been
> > there"
> > and generates friction. And low-quality discussions like that don't
> > attract smart people insights, precisely.
> > It's a vicious circle.
> >
> >
> > --
> > PHP Internals - PHP Runtime Development Mailing List To unsubscribe,
> > visit: http://www.php.net/unsub.php
> >
> >
>

--f46d043be1c684c6dc04b9ff116b--