Re: Scalar type hinting
| From: | Kiall Mac Innes | Date: | Thu, 01 Mar 2012 11:10:41 +0000 |
| Subject: | Re: Scalar type hinting | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-58408@lists.php.net to get a copy of this message | ||
On Thu, Mar 1, 2012 at 9:00 AM, Lester Caine <lester@lsces.co.uk> wrote:
> Both provide something that a large number of people did not or do not
> want anything to do with.
>
I disagree - The majority of PHP developers I've discussed this with are
in favor of adding *something *like this. Do a majority want this? I have
no idea and, I honestly don't believe you do either.
> Namespace was forced on us in much the same way you are currently trying
> to force this on us.
>
Forced? Nobody is forcing anything. Discussions are happening, and possibly
a vote in the future. This is the farthest thing from being forced IMO.
> Many people who were pursuaded that namespace was a good idea are now
> realising that it wasn't and was the thin end of wedge which this
> discussion is once again trying to force open.
>
Many of the popular frameworks have made the changes, or are planning to
make the changes, needed to take advantage of namespaces. This, to me,
suggests a general acceptable of namespaces.
Also - I'm yet to hear a single complaint about namespaces
- although again, I've not talked to every PHP developer!
(Well.. No complaints other than the namespace separator being a '\' that
is)
> I have no objections to 'object orientated' as that is how I have always
> used PHP, but the BULK of the data I am handling is simply strings which
> 'magically' get converted to the format I need. I don't see any use for
> 'type hinting' in any form since I NEED to check if a string I get in has
> the right data in before I store it in a database field. I don't need to
> throw some random error which needs handling ... I just handle the errors
> in line as I process the data. My framework helps to ensure what I get in
> is right in the first place anyway, so even the in-line checks are probably
> redundant nowadays!
>
I can certainly agree with you here - have I ever absolutely NEEDED this?
Nope. Would it get it the way of writing code in certain situations? Yup.
But - Does that mean it's not generally useful? Nope!
Kiall