Hi! > Admittedly Foo|Bar is of limited use, although there is some use. > Foo&Bar, however, has plenty of uses.
That is a different topic, not related to exceptions at all. > I do agree with the sentiment that having Foo|Bar for catch but not for > function signatures is going to confuse people. Confuse which people? Do people now are confused that you can write multiple catch clauses for same exception but can't write multiple function bodies for same parameter set? Are they confused by the fact that it's a fatal error to pass wrong type to a function but catch just silently ignores it? Are they confused that you can write function(string $a) but you can't catch(string $a)? I don't think so. I think people are pretty good at figuring out exceptions and function parameters are different things. Java has multiple catch and no expression types, and .net has the same after a fashion (with somewhat weird syntax) but programmers on neither wonder around confused expecting to find type calculus somewhere. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
