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?
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|