IMO, I think keeping the same name for that function in the different namespaces is not only reasonable, it's preferred. The same 'check' is being done on all 3 object types, so there's no reason to pretend they are different. And from the standpoint of the Dictionary and higher grouping functions, your OOP should be hiding the recursive nature of that function call to the end developer. Typically in other OOP languages, when classes have a similar behaving non-inherited method, the designers typically have the method name the same as to avoid extra terminology in the API.

Now, however, I would try to make sure that the variable you use are more descriptive than just $d or $e, if this code will be seen by others, unless no abiguity can be inferred. This way, it's understood that you're doing a consistancy check on a dictionary object or a entry object, as opposed to figuring out what each is.

-----------------------------------------------------
Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain
"I can see my house from here!"
It's not what you know, but knowing how to find it if you don't know that's important

In reply to Re: Question to OO Masters (about Style) by Masem
in thread Question to OO Masters (about Style) by PetaMem

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.