If I thought it was a problem, I might have thought to investigate it before hand so toxic people wouldn't attack for having a conversation with people about a weird thing I saw and wondering about it.

Is this a friendly place or is this a rule-bound hostile place where people can't pose ill-defined symptoms.

If I needed any help debugging a program, I might consider that advice, but more often than not, I'm posing ideas or questions that don't involve code -- something I want other people's opinion on or to bounce ideas or thoughts off of.

Sorry, but claiming I should have followed a writeup on asking a question about a behavior I saw, but had no test case for until another anonmonk tried to shutdown discussion about whether or not it might be a bug and gave an unrelated example to prove it, is a bit rule-bound and rigid.

So far anonmonk as tried to shut down discussion, then said that code that reproduced the problem wasn't a valid minimal test case (like anyone claimed it was). And then whined about the question not being posed in a way that their rules applied.

Is the anon-function ever used for anything useful, or just to harass and generate toxic comments?

Seems to me it's being abused and given the nature of this being a technical discussion board, and not a life-counseling center, I see no reason why it should even have an anon-function.

Whether it is a bug, "per se" ignores whether or not it is desirable or helpful behavior.

But that gets back to the purpose of the software being to *help* the users of it -- not to gratify the ego of those who dominate it -- an opinion that I definitely seem to be in a minority of around here.

Your attitude stinks.

In reply to Re^7: UPDATED, mostly solved: separation of define + assignment different from combination? by perl-diddler
in thread UPDATED, mostly solved: separation of define + assignment different from combination? by perl-diddler

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.