for java, I like capachino in a table mug or latte in a travel mug. But Ethiopian and Kenyan and South American beans can be nice too, I don't hardly insist on javanese beans.
(Java is slower than C++ and uglier than SmallTalk. Small teams build more faster, hows that working out?) seriously ... If you liked Deitel&Deitel on C++ and Perl and ..., you probably will like their Java text too. All examples are complete and run. But as with most textbooks they're aimed at novice programmers, explains stuff you already know. I once had notes on how to teach Java for C++ Programmers with Deitel&Deitel, but haven't seen those notes in ages. The real learning problem with most OO systems is learning the 'patterns' that work with the included object library. The Java library stack and preferred patterns have evolved greatly with Java, it's like they discard 50% of the stack each year. no point learning the stack that your customer has rejected or hasn't adopted yet. I would suggest actual language reference for quirky syntax rules, and the online Javadoc pages for whatever lib stack your customer thinks is the cats pyjamas. From there, read the customer's app's Java doc and then their code. If their code was well architected, you'll understand it's style and java by the time you're done ( and if not, you can't make it worse). -- Bill [email protected] [email protected] _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
