On Tue, Feb 28, 2012 at 2:53 PM, John Crenshaw <johncrens...@priacta.com>wrote:
> OK everyone, it seems that some people have forgotten or missed the
> original agreement that this thread started with. There is a communication
> disconnect ("strict typing" means horribly different things to different
> people right now). Please read through and understand the following
> terminology before continuing to post on this thread. We've agreed to the
> following terms:
>
> - "Strict Typing" means the super strict old C style typing *with no
> implicit conversions*. (If you really think this is what you want, you are
> probably mistaken. Look through prior discussions on this topic. This fails
> for numerous reasons, including the fact that almost every input to PHP is
> a string.)
>
Where is the term "strict typing" coming from? I've not seen this used to
describe any type system (doesn't mean it's not been used, but I'd really
like to see the usage so I can understand the label.)
> - "Weak Typing" means types in the same sense that the PHP documentation
> uses types (for example, the docs indicate substr(string, integer), and
> substr(12345, "2") == "345".) (If you think you want "strict typing", this
> is probably what you mean.)
>
Doesn't weak typing mean that the language implicitly converts types for
use according to a set of rules? The opposite of this being strong typing,
which means the language does not perform implicit conversions.
> - "No Scalar Typing" should be used to indicate the current system (where
> there is no provision for hinting at scalar types.)
>
And, curious about the "No Scalar Typing"?
Sorry for the questions.
Thanks,
Adam
--
Nephtali: A simple, flexible, fast, and security-focused PHP framework
http://nephtaliproject.com
