-- This curiosity is my main drive,

I have no desire to indulge your curiosity. I have enough of my own to deal with.

-- your way of asking questions that provokes replies that you don't like.

If you mean, asking only the question to which I want the answer, without providing extraneous information on which interefering busy-bodies can hang their coats, perhaps. But, it doesn't work because those same interfering busy-bodies will invent reasons to indulge themselves.

In this particular case, I have been using a solution to a particular problem for a while. I works, but has a flaw. I saw Scope::Upper and it sounded like a possible solution to that flaw, but I couldn't make it work, so I asked my question. As soon as tobyink posted his reply, I saw my misunderstanding, and realised that Scope::Upper could never provide the solution I was hoping for. Job done. Or should have been.

Instead. We get all these useless subthreads 992853, 992889, 992952 that could never be of help to me, because they make no attempt to answer the question I asked.

I do not give a flying fig whether you feel Guard is a better solution to your imagined application, than Scope::Upper.

I do not give a flying fig whether tye thinks his imagined application for Scope::Upper will "break encapsulation", despite that it could not for mine.

I have no interest in debating either. If I had wanted to solicite suggestions for a solution to my application, I would have asked that question. I did not.

I do not give a flying fig whether you or anyone considers that I have asked the wrong question. I ask the questions I ask, because that is what I want to know. I ask them in the way I do, because I want just that answer, not a debate about other approaches, alternative solutions, alternative questions.

If you don't know the answer to the question, don't answer it. If you do know, but don't want to answer (either it or me) that is fine too.

In reply to Re^12: Scope::Upper localize? by Anonymous Monk
in thread Scope::Upper localize? by Anonymous Monk

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.