I think Masem is absolutely right. In your example, which may or may not be realistic, you have a different problem than what you're asking about.

If you spend energy (well done) to figure out the best naming conventions for your methods in different classes, then you should probably spend a minute or two thinking of the naming of your variables in your non-OO sub.

$c and $d may be commonly used (and make sense) in a small Perl script. But in any bigger script, including the design of several class modules, these variables should probably be named in a more descriptive way.

$d->semcheck can be made a lot more descriptive by using $dictionary->semcheck().

$dictionary->semcheck() and $entry->semcheck() already reads out more clearly.

f--k the world!!!!
/dev/world has reached maximal mount count, check forced.