in reply to Formatting variables

crmr_5 Read access to business unit 5 crmw_3 Write access to business unit 3 crmn_1 Read and write notes access...

I would do something like:

my $ro_business_unit_5; my $wo_business_unit_3; my $rw_notes;

I would much rather have long variable names that I can absolutely, unambiguously know what they represent, than having to wade through code trying to find the original assignment. To boot, typically if someone is using non-descriptive variable names, they likely are naming functions ambiguously as well, which makes it doubly as hard to sort out the true meaning behind the variable name.

Some people say "I have to type more if I use long variable names!", to which I say, get a better editor/IDE that does variable and function auto-populate. If they don't want to do that, then they can contemplate later down the road how much time they would have saved by typing the long var names as opposed to trying to look through thousands of lines of code figuring out which variable does what six months after they last looked at the code.

Replies are listed 'Best First'.
Re^2: Formatting variables
by Fletch (Chancellor) on Nov 29, 2020 at 17:43 UTC

    Seconded; with something like company mode you just have to pick from a list or hit a key to cycle through the alternatives.

    Also whenever you have a family of variables (e.g. named with suffixen or indexen) it's a red flag that you probably want a data structure (as was mentioned above but linking to MJD's article with more commentary).

    The cake is a lie.
    The cake is a lie.
    The cake is a lie.

Re^2: Formatting variables
by Bod (Friar) on Nov 29, 2020 at 19:29 UTC

    Some people say "I have to type more if I use long variable names!"

    Even without a better editor/IDE, slightly longer typing variable names seem like a reasonable trade off for easier to maintain code in the future - be that next week or next decade.