Paule Ecimovic wrote: > From: "Rob Kennedy" <[EMAIL PROTECTED]> >> In most cases, nothing. I think there have been a few more reserved >> words added, but the chances you've used them are low. Some classes and >> functions have moved to different units; you may need to use the >> Variants, StrUtils, or DateUtils units where you once simply used >> SysUtils. >> >> Open your project in Delphi 2005 and let the IDE and compiler tell you >> where the problems are. > > I wonder how best to follow the revision trial from Delphi 4 to Delphi > 2006 indicating refactorings of the Delphi VCL, which might lead to trouble. > Would it be worth making a dynamic tree structure with highlightable > branches which would indicate refactorings?
I think that would be a lot of work for not a lot of gain. "Refactoring" is a strong word for the changes that took place. Functions and types were moved into different units. That is one way of refactoring a project, but it's not on the same level as creating new functions for common code or changing the ancestor of a group of classes. If code used to compile in Delphi X and it doesn't compile in Delphi X+1 by reason of an unknown identifier, then the identifier is probably in a different unit. Simply search for the identifier in the VCL source code to find the correct unit. You might not even need to search if you know what the function is for: If Delphi doesn't recognize a Variant-related function, for example, use the Variants unit. -- Rob _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
