Hello Daniel, Sunday, May 25, 2008, 4:30:32 PM, you wrote:
> Hi Marcus: > On Sun, May 25, 2008 at 10:57:22AM +0200, Marcus Boerger wrote: >> Saturday, April 5, 2008, 3:27:33 PM, you wrote: >> >> We experimented with visibility and ran into trouble. > ... >> So we in fact note the visibility but then ignore it. >> >> I think we either need to respect the visibility or issue an error if it >> is not public. Please file a but report. > Turns out, one already exists: http://bugs.php.net/bug.php?id=44769 >> > * The value of $name in __call() is case sensitive, but in the newly >> > added __callStatic() $name is lower case. Is this intentional? It seems >> > the two methods should have the same behavior. >> >> It isn't for function calls so this is the correct behavior. > I don't understand your response. Can you please clarify? Oh, actually it is my fault - I've read this part wrong. So infact __call is case sensitive. This is becasue the engine is indeed case sensitive up to the final lookup all over the place. We do that so that we can produce case sensitive error messages. So not doing a down case just enables the same behavior for the user. The other reason for making __call case sensitive is that an overloaded object might need the correct casing information. That said there is a bug in __callStatic which we need to report and assign to Sara. > --Dan > -- > T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y > data intensive web and database programming > http://www.AnalysisAndSolutions.com/ > 4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409 Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
