If defining tied and OO interfaces, you must define duplicate functions or use typeglobs. Some parts of the syntax are, well, kludgey This RFC attempts to address all of these points with some changes to syntax and implementation concepts. All other functions are directly translated via the indirect object syntax. This eliminates one more special-case function which currently requires that quotes be placed around the class name. And, creating a class that supports both OO and tied interfaces is difficult, requiring typeglobs or duplicate handler functions.
Translation is potentially much faster because the indirect object syntax is used.
This provides true object transparence. Drop internal function translation and instead translate based on modified indirect object syntax 4. In any event, this is a massive oversimplification, but at the very least it sheds some additional light on the concept. As such, the p52p6 translator should be able to change this relatively easily.