Patches welcome. (This is usua... nevermind *grin* - Juerd) I'm sure that if you write a good tutorial, it will be included in the main distribution. Just wishing for things isn't going to make it happen - someone will have to write it.
It seems my rant was posted a bit too soon, as perlintro is a nice tutorial for beginners. It doesn't cover everything I think it should, but I guess it's a matter of time before more docs get into the distribution. I myself am not a good writer, so I won't be the one to write a tutorial.
I posted this to find out if there is already a tutorial that is accepted as "the best", but there hasn't really been an answer to that yet.
Don't take this the wrong way. This is how Perl is being developed. The surest way to get things added/changed is by just doing it, and submitting the patch.
Maybe someone here wants to write a good tutorial that covers everything? Or wants to convert an existing one to pod? Perhaps the document we're searching for already exists, but just isn't named perltut?
My post isn't just a "hey, I want this and you should make it happen" post: I want to know how others think about this and whether what I'm wishing is sane.
- Yes, I reinvent wheels.
- Spam: Visit eurotraQ.
-
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.
|
