At 12:02 PM 2/11/03 -0500, Sherm Pendley wrote:
Here, Here. Perl will happily let you shoot yourself in the foot, but we should always keep in mind that the target is downrange, not straight down. I think that is why good perl programmers have to be disciplined - the language doesn't force it down your throat. This can be good or bad depending on your viewpoint/skills.On Monday, February 10, 2003, at 11:04 PM, Erik Price wrote:You say that as if it's a bad thing, or as if it applies only to Java. I've also seen quite a bit of Perl that would have benefited greatly if the author had put some planning into it before he started busting out code.Java doesn't let you just bust out what's on your mind -- I've discovered that you really have to plan out your application's public interface
That is great for those 1-off scripts that you just "bust out", but for a real application intended for long-term use in production, a little planning goes a LONG way. Just try maintaining those "busted out" scripts a year down the road when all the original programmers are gone and you're trying to add a new feature. Except it's extremely difficult to even get a grip on what's happening because they used tons of scalars instead of a hash to keep track of the current screen. (this has never happened to me...)
Drew
--
Drew Taylor | Web development & consulting
http://www.drewtaylor.com/ | perl/mod_perl/DBI/mysql/postgres
----------------------------------------------------------------------
Netflix: DVD Rentals by mail with NO late fees or due dates!
Free Trial - http://www.netflix.com/Default?mqso=36126240
----------------------------------------------------------------------
_______________________________________________
Boston-pm mailing list
[EMAIL PROTECTED]
http://mail.pm.org/mailman/listinfo/boston-pm
