debug_backtrace() output reveals implementation details?

[cpriest]

Same as #14, what does current output look like and what do we want it to look like.

[nikic]

Instead of function => __getfoo I'd use property => foo and accessor => get in the debug backtrace. Do those names sound good to you?

[nikic]

One complication that I see with this is that it would use the new format always, not just when called via a property. But as the internal functions aren't supposed to be directly called anyway that shouldn't matter, should it?

[cpriest]

When you say the internal implementations, do you mean auto-implemented __getFoo()? Are you saying that an auto-implemented __getFoo() would not be callable directly or be listed as a method of the class?

I think that's no good...

[nikic]

Now the backtrace includes "function" => "$foo->get". I guess that's better for users as they don't need to specifically distinguish between function and property in their use. One might add something like property+accessor additionally though.

[cpriest]

Yeah, I think this is just fine.