Re: Resolution of static variables in the function scope not using forwarded calling information?

> This last is the only one that seems to be a bug to me; I think if you > step through the others you'll see why they are fine. Maybe the last > isn't a bug either; I'll try to think about this more but it does > appear to be a bug. FWIW, an example that makes the second situation slightly more clear: http://3v4l.org/CcrL8 I would have expected the static function variable and get_called_class() to always refer to the same class/variable space, parent:: or not. Oddly enough, referring to static class variables with "static::" never seems to use late static binding at all? http://3v4l.org/G9nCE Thanks, Laszlo