It's like "try this, or try that", or "this does this and that does this". That's all well and good, but how did you decide to try this and try that?
I addressed this in the first JAPH talk I gave. It went like
First you get an idea, then you work out the details.
Getting the idea can come from many sources: studying the
manual page, reading Perl forums like comp.lang.perl.misc,
p5p, The Perl Journal, or from IRC. If you look at my first
set of slides, there's a section labelled "The making of a
Japh". It discusses the process that started with seeing someone use
&%%hole in a non-Perl related usenet group and
ended with the Japh:
split // => '"';
${"@_"} = "/"; split // => eval join "+" => 1 .. 7;
*{"@_"} = sub {foreach (sort keys %_) {print "$_ $_{$_} "}};
%{"@_"} = %_ = (Just => another => Perl => Hacker); &{%{%_}};
(The code above will not always work correctly with 5.8.1
or later).
Abigail
-
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.
|