On Jun 26, 2009, at 8:33 AM, Bobbi Fox wrote:
There are whole swaths of Java I learned in class that I have *never* used (all the SWT stuff), so, if you're in do-it-yourself mode, figure out what it is you want to accomplish.
I'd second this. In many ways, the strength of Java is the same strength of Perl: the vast libraries available to you. Java has a ton bundled with it, but in many ways so does any modern perl distrib. So some of your perl habits (such as always checking CPAN first) will pay off in Java (always do a google search or look at the Apache foundation).
Don't work against the Java libraries or the language styles--embrace them. For instance, if you use "_" instead of camelCase for your perl variables, switch to camelCase when in Java. Don't fall into the trap that so many do of "writing X language in Java"--it will be an awful experience.
The camelCase stuff, getter/setter conventions, class naming, etc will not affect your code--but it will affect how you make "context switches" from perl to Java. Every language is a tool that works best when you embrace its methodology and design. When Java programmers come to Perl and write Java-like Perl, it looks ugly and often has gross inefficiencies. The same goes the other way.
And definitely pick up Eclipse. I recommended it at the last PerlMongers for simplicity; MyEclipse is great for the price and for the simplicity of just having one install package that gives you just about everything you could ever need.
http://www.myeclipseide.com/ Good luck! Matt -- Matt Luker */rsh tech your source for programming know-how phone: 617.418.3480 email: [email protected] web: http://www.rshtech.com/ _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
