Other than calling it specifically my model, I can fully endorse this post. I don't prefer one model over the other, as I still don't see a definite general-case benefit to one or the other. I just like to defend the model that people criticize if I see merit in it. I'll also criticize a model others endorse if I see flaws. I'll even defend the strong points and criticize the weak points of the same model.

In specific cases, I think this one helps some people. In other specific cases, I think the model ysth, tye, JavaFan, merlyn, and yourself use is more helpful (and more precise with relation to the actual implementation).

Mostly I like for people to be able to choose which one works for them. I've avoided disclosing my particular mental model up to this point because I don't think that how I personally think about it when I program is that relevant to whether or not a particular model is useful to others.

If people really must know...

<Reveal this spoiler or all in this thread>

You do recognize and understand the workings of the model as I understand it, though, and I think it admirable you went through the trouble to do so.

In reply to Re^19: If you believe in Lists in Scalar Context, Clap your Hands by mr_mischief
in thread If you believe in Lists in Scalar Context, Clap your Hands by gone2015

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.