Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59890
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F87C9B0.4080809@gmail.com>
References: <CAKOpQSwYe+tZ3JfLFWaOHCnBpUyy9yoA61=qLzbnnOKTL0mQdQ@mail.gmail.com>
	<CAGa2bXa554p45tbNFvtHQJiYTXaa0eD6r+qnExDVk+6e8PRvMw@mail.gmail.com>
	<4F876943.8030105@gmail.com>
	<CAKOpQSzAZauE9HYK3x-5UbxAstkdkc-HkfZRa+E+i=DNxQwkBA@mail.gmail.com>
	<4F877777.8050806@gmail.com>
	<CAKOpQSyC6Zs=3-AQ8=L-aufTP03j0yhnRiu3n6pNP7YSpW_KLg@mail.gmail.com>
	<4F8782CC.8030205@gmail.com>
	<CAKOpQSzKo9ZX1voYppTRihkfkpfCywMLLv_DF8XWGxcOV1Su8Q@mail.gmail.com>
	<CAGsnKxaR8vHHeZrpDhf4WVBKqDwMXrAf=b=3r06oJZpP4K3sPg@mail.gmail.com>
	<CAKOpQSyVu3ddZubCeo4BpZTWFXf55_yYNbrhDqTJkDjPoX6xVw@mail.gmail.com>
	<CAGsnKxatwB-T5ExGjq9z0FyjhRB0DKVRigu=opqXbjoyUAcwRA@mail.gmail.com>
	<CAKOpQSy3BVpY-UNSvVkQSoPBV=ZKdiJ0nOC14ou3YRdJM5XmnQ@mail.gmail.com>
	<4F87C9B0.4080809@gmail.com>
Date: Fri, 13 Apr 2012 10:41:03 -0700
Message-ID: <CAKOpQSz-hMYHpcrs_f5vKmZTKvvAckJwNswsK33xqJ49fN3=6A@mail.gmail.com>
To: David Muir <davidkmuir@gmail.com>
Cc: John LeSueur <john.lesueur@gmail.com>, internals@lists.php.net
Content-Type: multipart/alternative; boundary=f46d04389347ffb38b04bd92f906
Subject: Re: [PHP-DEV] [RFC] New .phpp File Type for Pure-Code PHP Scripts
From: kris.craig@gmail.com (Kris Craig)

--f46d04389347ffb38b04bd92f906
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Apr 12, 2012 at 11:37 PM, David Muir <davidkmuir@gmail.com> wrote:

> On 13/04/12 15:13, Kris Craig wrote:
> > Again, the controller should NOT be a .phpp file.  Likewise, your model
> > should NOT be hooking directly to the view.  The controller hooks to the
> > model.  The controller then sanitizes that and returns it to the view.
> >  Alternatively, if you're not conforming to a pure MVC standard, the
> > controller can also hook to a regular .php file in the model and pass the
> > data to that.  Either way, it all passes through the controller.  The
> model
> > and view should never be interacting directly.  MVC or not, that's just
> bad
> > architecture and there are zero advantages to using such an ad hoc
> approach.
> >
> > If a developer insists on using such a broken model, however, they're
> more
>
> MVC is a broken model/bad architecture?
>

Arrooo?  Not sure where you got *that* from, as it's basically the exact
opposite of what I said....


>
> > than welcome to!  That's what people love (and hate) about PHP.  It's
> > flexible.  They just won't be able to use a .phpp file upstream from
> that,
> > as it is by its very nature inherently incompatible with such a broken
> > model.  The only way to force it to be compatible would be to make the
> > .phpp file essentially meaningless.
> >
> > So if you're writing good code structure, a .phpp file will help you make
> > it even better.  If you're writing bad architecture, then just keep doing
> > what you're already doing and don't worry about using a .phpp file!  This
> > will in no way stop you from being able to do what you can already do in
> > PHP.  You're just insisting on wanting to use a pure code file for
> > something that it's not intended to be used for.  Just like having object
> > orientation added in PHP 5 didn't stop you from writing procedural code
> if
> > you want to, introducing this in PHP 6 won't stop you from writing
> > disorganized code if you still want to.  What this will do is provide a
> > valuable option for people who do feel that writing clean,
> role-segregated
> > code is important.
>
> So basically, the only parts that might be ok to write as .phpp are some
> model and utility classes?
>

Essentially, yes.  Despite your implication, often times these components
make up the vast majority of a modern PHP application.


>
> David
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--f46d04389347ffb38b04bd92f906--