I have thought about this ever since the discussions started that PERL 6 will a big change.. and what I've come to is that when it is out I will start to learn the basic changes, if what i see seems to fit the way i think a little better then i may start getting more in depth and maybe start porting some of my stuff as an exrsise to see whether I like it better or not.
What I think will really get me over there is what happens with CPAN. At first most of my code will stay PERL 5 since that what the modules I use are in, when really cool new modules come up or improved version of the ones I use now start showing up written in 6 and expecting to work with Perl 6 then I will really sart to switch over in ernest.
I got into perl because i was working on problem that was turning into a real pain in shell script and someone pointed me to a very simple PERL solution, I suspect the same will happen with 6 when I have a problem that is easier or cleaner to solve in Perl 6 than in 5 then I will really have the motivation and the willingness to learn the new stuff.
-
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.
|