Wedge
Public area => Bug reports => The Pub => Archived fixes => Topic started by: Bunstonious on February 20th, 2014, 03:29 AM
-
On my work laptop with IE 9 I am unable to browse to Wedge.org and get the attached error.
Works fine in Chrome, not a big issue just reporting it (could happen to other peeps).
(http://home.bunston.net/images/wedge-error.png)
-
It's probably not due to IE9, but I'll have a look.
That's really strange, that error message...!
That line is part of wess_rgba, which extends wess, so it CAN access its protected methods. It's one of the basic principles of PHP5 OO...!
Maybe it's a problem with the lambda function. Hmm... That would be ridiculous. :-/
-
It may not be IE 9, but it's weird because it doesn't happen in Chrome.
-
Well, it doesn't appear when the function isn't executed. I haven't looked too much into it, but that's what's happening... I guess!
-
*shrug*
I'll just use Chrome.
I might see if I can sneaky check one of the citrix IE's.
-
Just make sure to test the latest version in IE9, and mark this as solved ;)
-
Oh hey it's working... WIN!!!
How did you fix it? What was the problem?
-
Well... I did post a new commit earlier today saying that I'd reverted the function change... :^^;:
This is due to a PHP bug, where closures enclosed within a class method can't call protected or private methods that would normally be available in their scope. Since closures are precisely supposed to be functions that inherit their context's visibility settings, it's really what I'd call a bug.
Hopefully, this problem will only be obvious in that function. But really, enough to make you think twice about going for a 100%-closure codebase, I guess... So much for PHP 5.3 being a must-have?
-
I try to read the commit logs, but I am not that programmer savvy yet :P
PS: thanks man, you are probably the friendliest project main developer I have seen.