Dominic Burford <> wrote: > << > I must say that for large projects involving multiple developers and > changing requirements, strong, static typing speeds things up, simply > because refactoring is so much easier to do. >>> > > I'm curious to find out how. I would have thought a strongly typed > language would have been *more* difficult to refactor, for the same > rasons that it can take longer to develop using them i.e. they can > prevent certain object interactions due to their enforcement of data > types, and thus leads to additional code being written which conforms > to these constraints.
I work in a strongly typed language and find this totally FALSE. It is easier to refactor in C# /VS2005 then any other IDE I have worked in. In VS2003 it took a little more time. Just hit Build and it would find all the parts missed in a single refactor of a method used all over your app. Now "thus leads to additional code being written which conforms to these constraints." OK this is a valid POV from a VFP person who says I just need to add a day to my date. dDate = dDate +1 dDate = dDate.AddDays(1); So it is more verbose, in that you have to define what your adding to the object. But you do get more out of it. dDate = dDate.AddMonths(2); dDate = dDate.AddYears(1); Stephen Russell DBA / Operations Developer Memphis TN 38115 901.246-0159 http://spaces.msn.com/members/srussell/ -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.5/377 - Release Date: 6/27/2006 _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
