Thank you all for your responses. As you can see from my original question, keeping format names in a hash as proposed by sundialsvc4 was the solution I was trying to avoid, hopeful that there is more efficient way through direct access to format namespace. Alas, there seems to be none, so storing names in the hash seems to be the only good way to reuse formats in my context.
I did look at using formline() as illustrated by Anonymous. It allows to avoid ugly eval, but it guarantees that format will be created every time swrite is invoked. Running swrite seems to be pretty much the same thing as running format, except there's no format name associated with it. It is definitely a strong alternative to eval approach when reusing formats is unimportant (e.g. when formats are different for each line). Thanks again everyone!

In reply to Re: caching formats by hotpelmen
in thread caching formats by hotpelmen

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.