Re: How do I train myself to write more Perl-ish Perl, rather than C-ish Perl?

Just a suggestion, but read one of my columns each day. Even if you don't completely understand the problem, the solution, or the explanation, you'll see a lot of "native" Perl code of varying levels. And you could go for 255 days before needing something else to do. :)

And seeing code (a lot of code) written by "native" speakers is really the only way to "get native".

-- Randal L. Schwartz, Perl hacker

Comment on Re: How do I train myself to write more Perl-ish Perl, rather than C-ish Perl?

Replies are listed 'Best First'.
Re^2: How do I train myself to write more Perl-ish Perl, rather than C-ish Perl? by amarquis (Curate) on Dec 14, 2007 at 15:31 UTC
I've read your columns sporadically in the past, and they've been very useful because I've found ones that were very close to issues was dealing with at the time. Thanks for writing them :). Edit: Now that I think about it, lack of native immersion is probably one of the big reasons my progress is slower than I'd like. At my jobs, I've always been surrounded by Java or C++ guys, or PHP/Python guys. Add to that the fact that I'm not using Perl all day, and Perl doesn't end up with the brain share I want it to have.	[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.