note tobyink <p>The one place I find this sort of thing useful is where you're dealing with a bunch of different pieces of data, some of which are in a "processed" state, and other in an "unprocessed" state.</p> <p>For example, you have a <c>$title</c>, <c>$author</c> and <c>$body</c> for an article; the <c>$body</c> is stored in your database as a blob of HTML, so doesn't need entity encoding when you pump it into an HTML template, but the other two are stored as text in the database, so need entity encoding when inserted into the template.</p> <p>So I'd call them something like <c>$title_txt</c>, <c>$author_txt</c> and <c>$body_html</c>.</p> <p>Other examples might be where some of your bits of data are UTF-8 encoded byte strings, and others are Unicode character strings; or some bits of data are tainted and others are not; etc.</p> <div class="pmsig"><div class="pmsig-757127"> <small><small><tt>package Cow { use Moo; has name => (is => 'lazy', default => sub { 'Mooington' }) } say Cow->new->name</tt></small></small> </div></div> 1014477 1014477