Caché Upgrade Checklists - InterSystems Documentation

Developers7.1.9.5 Windows 64–Bit: Studio Activate Wizard UnavailableThe Activate Wizard is currently supported only on 32–bit windows platforms. It is greyed out on the Studio Tools menufor 64–bit systems.7.2 DevelopersThis section contains information of interest to those who have designed, developed and maintained applications runningon prior versions of Caché.The items listed here are brief descriptions. In most cases, more complete descriptions are available elsewhere in the documentation.7.2.1 Compatibility Notices7.2.1.1 ObjectScript Compiler VersionThe ObjectScript compiler has been modified to improve code generation. This change is significant and internally theminor version of the compiler has been incremented to mark this. Code for routines or methods compiled in this versionof Caché will not run on previous versions.7.2.1.2 Class Component SignaturesThis version of Caché corrects a deficiency in the class compiler in versions 2007.1 and 2008.1. Existing classes thatcompiled without error in those releases may now be recognized as having signature errors in some overridden inheritedcomponents.7.2.1.3 Property ReferencesThis version of Caché corrects a deficiency in the class compiler that existed in earlier versions. References to propertiesmust have an instance context; you cannot GET a property without giving the OREF for it.This change also affects cases where an applications called propertyGet() methods as class methods. For example, applicationsusing ##class(name).property to call the propertyGet() will have to change to call a proper class method. Such calls willnow result in an error. These method calls should be rewritten as class methods instead of calculated property.7.2.1.4 Preservation Of $TEST Value Across CallsIt is documented that the value of $TEST is preserved across calls to any procedure. In prior versions, however, this wastrue only for calls to procedures defined in the same routine as the caller. Caché has been changed in this version so thatthe value of $TEST is restored regardless of where the called procedure is defined.7.2.1.5 Change To Storage Global Name GeneratorThe name of the global used to hold the storage for instances of a class is derived from the fully-qualified name of the class;that is, package name and class name. If the length of the resulting name exceeds the maximum global name length, theclass compiler may truncate either the package name, class name or both to generate a global name that fits within thedefined limits.Caché Upgrade Checklists 171