My guess is that the code you are dealing with doesn't have that many coders and so doesn't warrant such aliases. But this is an issue to be decided by the development team.

I tend to tough it out in such situations--sharing a vocabulary promotes communications; adapting promotes flexibility of thought. I get interrupted enough that maintaining flow is pretty hopeless.

Perhaps you could wedge something like this into your checkouts:

#!/usr/bin/perl

use warnings;
use strict;


# rirs_lib

sub A::isGods {
    use Carp;
    carp "Warning: rir's idiocynatic call s/b isGod$/";
    A::isGod(@_)
}


package A;

sub isGod { local $,="|" ; print 'You are God ', @_, $/; }

sub new { bless {}, 'A' }


package main;

my $g = A->new();

my $what = "what";
my $else = "else";

$g->isGods( $what );

A::isGods( $what, $else );


__DATA__
Warning: rir's idiocynatic call s/b isGod
    A::isGods('A=HASH(0x814ccd4)', 'what') called at ./xx line 30
Warning: rir's idiocynatic call s/b isGod
    A::isGods('what', 'else') called at ./xx line 32
You are God |A=HASH(0x814ccd4)|what|
You are God |what|else|
[download]

Be well,
rir