Hey now. It wasn't entirely unsupported. We'd had chatterbox conversations about it where I mentioned stuff. Then the May holiday came up, I found myself busy and tkil looked like he/she was being thorough.

The one thing I really want to add at this late date is that as a consensus, we don't view things like strict as something theoretcally nice for school or such. I use it because it is a really practical, day-to-day, help me write solid-code, fast, thing to do. I understand why VarStructor exists - to assume that a program's state exists in a bunch of shared variables in a common namespace and then clear or examine them. The thing is, with lexical scoping (my) we've (meaning the productive part of the perl community) moved onto better things and as a matter of course either have no globals or as little as possible. That's the big thing. The part where you use eval just makes it possible for someone to break your code. The part with source code parsing makes your code fragile. Its like going out and putting a bunch of well know and identified weaknesses into your program. It just sits poorly. Do you understand that viewpoint?


In reply to Re^4: Wassercrats::Improved Volume 0, Number 0 by diotalevi
in thread Perl::Improved Volume 0, Number 0 by Wassercrats

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.