On Mon, Mar 5, 2012 at 4:35 PM, Shawn H Corey <shawnhco...@gmail.com> wrote:
> On 12-03-05 10:19 AM, lina wrote: > >> Is the books wrote before 2006 a bit older, are there much changes in >> the last 10 years for perl? >> > > All changes to Perl are available via perldoc. > > `perldoc perl` and search for /delta/. > > `perldoc pelrdelta` gives the latest. > > > -- > Just my 0.00000002 million dollars worth, > Shawn > > Programming is as much about organization and communication > as it is about coding. > > It's Mutual Aid, not fierce competition, that's the dominate > force of evolution. Of course, anyone who has worked in > open source already knows this. > > > -- > To unsubscribe, e-mail: beginners-unsubscr...@perl.org > For additional commands, e-mail: beginners-h...@perl.org > http://learn.perl.org/ > > > In general it is a good idea to read the information about what changed between then and now as there are some changes that will usually not break older code but will be the difference between a "Well written bit of code" and a "Outdated bit of code" but in general most if not all of the things you find in a good book from 2006 should still work now in 2012. As for a good book to begin with learning: "Learning Perl" (ISBN: 1-4493-0358-7) also known as the camel book would be a good place to start. Other things like websites such as: perl.com and perl-begin.org are good resources to have a look at as well. Besides that I personally learned most from finding a problem or a relatively simple thing that for which I thought a perl solution would be great. I then spend time and effort trying to figure out how to get this work done with perl. Of course this is assuming that you have some programming background already so you know how to tackle the work in what ever other language, all you then need to do is figure out the way to do this in perl. The main thing specially when you are learning what ever language is to have fun with it. Don't take on to much (you are not going to build the next Google empire in Perl after a week or so of practice) and to keep on asking questions when you run into something that you just can't get your head around. That does not always mean mean ask on this mailing list it could be as simple as using Google to find a good explanation that helps you understand the how or the why. Of course the usually friendly people on this mailing list are often happy to help. The best way to get help is to show what you have done so far and to as clearly as possible explain what it is that you want to do or are expecting the code to do etc... the easier it is to understand what you are looking for the more likely it is that people will be able to help you. Regards, Rob
