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:
Be well,#!/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|
In reply to Re: Are sub/method synonyms acceptable coding practice?
by rir
in thread Are sub/method synonyms acceptable coding practice?
by demerphq
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |