Whatever convention you use: use it, as long as it is good for you. It is good for anybody else too, if it's documented. But be consistent.

That said, I have the same uneasieness with splitting up $blivet into variables with a pre- or postfix as I have when I see $var_1, $var_2, $var_3 instead of @var.

If you have a thingy which is this or that depending on context and/or has some attributes associated, use a suitable container for them. This can be a hash or an object.

So, I'd rather say:

$blivet->file_name;
$blivet->file_rel;
$blivet->file_abs;
# and so on

[download]

Concatenating a identifier with a functional part - i.e. some kind of index - into a new identifier just looks wrong to me.

In reply to Re: Path Part Identifiers by shmem
in thread Path Part Identifiers by Xiong

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.