I'll delurk here for a moment, I am of the opinion that there is not that much of a need to allow for simultaneous access to similarly named Perl data types in python. I am not aware of any CPA modules that export two or more of the same name but for different data types - such as $foo, @foo, %foo, and &foo. While it appears necessary, on the surface, to allow for access to all of these types at once I think the need for such access is being overstated. Though it isn't my place to dictate style, exporting multiple types of the same name seems ambiguous and should be avoided - even if the module is only to be used in a straight Perl context.
I like that in the syntax Leo has used, there is no reference to what Perl type you are using. This seems to be the most natural way to merge the languages together. I don't know that bridges need to be built around gaps were languages do not perfectly merge together. If I export or place two data types with the same name in a "publicly" viewable namespace, I am fine that only one of them will be viewable in Python and will probably be chosen based upon type (so long as the decision about which is viewable is consistent). If the ability to reference all four data types at once is not easy to do from within Python as Leo has repeatedly stated, then it should probably be left alone. In this case being able to do something merely for the sake of being able to do it, doesn't seem to offer enough justification for the creation of new syntax in either language. Paul Seamons
