Tuesday, February 3, 2009

+CodeInspector 4.0

NEW features:

  • Public Scanner (OLE PUBLIC class), which makes it possible to empower your VFP projects with +CodeInspector functionality. Learn more...
  • Report file now has information about declared but never used variables
  • Scanner now performs a check for the following:

    • commands which are not supported in run-time mode;
    • multiple return instances;
    • too nested constructions;
    • repeated declaration of variables;
    • re-declaration of variables (e.g. with changing private type into public and so on.)



IMPROVED features:

  • Improved the check of variables declaration in nested constructions. E.g. variable declared within the first part of construction "If-Else-EndIf" and used in the second part of it, is treated like error.
  • Checking of lines starting with "\" and "\\" constructions is disabled
  • NOTE comments are now supported

FIXED bugs:

  • Fixed error of scanning files larger than 64000 lines
  • Fixed error of scanning commented lines of code

+CodeInspector 3.6

NEW features:

  • Protection from scanning forms and classes created in VFP 2.0 and 3.0.
  • Added six new system variables: _memberdata, _menudesigner, _reportbuilder, _reportoutput, _ reportpreview, _tooltiptimeout.
  • Full checking of "Microsoft Visual Foxpro 9.0 Samples and FFC" revealed 3200 errors. You can use the scan report for free. Note: duplicate names of forms and classes were changed (e.g. _toolbox.vcx renamed in _toolbox1.vcx etc.).

IMPROVED features:

  • Scanner core improved. There was an error while scanning program files, where variables whith same names as VFP keywords were used (e.g. command "func=1" was recognized as a declaration of new function)

FIXED bugs:

  • Error in defining parameters of function which creates variables in memory (e.g. local aSQL[ aSQL( aArray )] - this example shows the creation of an array named aSQL the size of which is created within function aSQL. Error occurs only when aArray is not defined, in previous versions aSQL was recognized as a variable and that caused errors)
  • Error of getting full path to the object method in the hierarchy of forms and classes (e.g. if the being checked method was located in Form1.PageFrame1.Page1.Container1.SetFocus(), scanner cut the path: Form1.Container1.SetFocus(), therefore it could not find the method)
  • Error of opening files for editing was also fixed. (If there was a space in file name, Internet Explorer changed it to %20 and scanner could not open it.)
  • Incorrect definition of trial period. (e.g. if you used trial version 3.0 and then after trial period expired you installed trial version 3.5 - you couldn nt use it)
  • Error of canceling "set notify on" option
  • Errors in +CodeInspector Quick Scan. Sometimes when scan was started for the forms opened in VFP editor with class different from "FORM" error "oObject not found" occurred. Also the procedure of report building for such forms was fixed (line numbers were incorrect).
  • Other small fixes.

+CodeInspector 3.5

NEW features:
  • Support of VFP9.  Integration with VFP9 IDE and new language constructions were added to the scanner core.
  • The following functions are also being checked now: ADLLS, ADOCKSTATE, AELEMENT, AEVENTS, ALANGUAGE, APROCINFO, ASESSIONS, ASQLHANDLES, ASTACKINFO, ATAGINFO.
  • The following instructions are also being checked now:
  • Text to <VarName>
    Scatter name <VarName>
    Scatter mamvar fields <VarNameList>
  • Scan progress is shown in a new dialog with Cancel button (before you couldn't stop the scan process).
  • The button for selecting a folder to scan was added in the +CodeInspector quick scan dialog. Now it's easy to scan all files under one folder.
  • It is now easier to go to the file scan report from project scan report by simple clicking on a file name.
  • If you click the method name in file scan report it will open the program file with this method and will set focus to the line containing first instance of this error.

  • IMPROVED features:
  • Projects are now loading faster at +CodeInspector startup.
  • Class library scan report now contains not only method name where an error was found but also class name which includes this method (Solution for multiple error instances in methods from different classes but with similar names. Thanks to Karl Madges!).

  • FIXED bugs:
  • Bug with multiple activation of "Scan this file" and "Skip this file" checkboxes fixed
  • Project list area in +CodeInspector projects dialog is blocked while scanning, to prevent async event processing.
  • Text and links in Registration dialog were edited.
  • Small bugs in the interface were fixed.

  • By the way, +CodeInspector 3.5 found 900 errors in Visual FoxPro 8 support files (FFC classes and samples)!

    +CodeInspector 3.0

  • NEW: Project window
  • Now you can work with several VFP-projects, scan files form different locations and more...
  • IMPROVED: multifunctional [+] button from the Quick Scan window replaced with 3 buttons.
  • IMPROVED: small additions to the scan engine.

  • +CodeInspector 2.4

  • NEW: Handling of Text...EndText constructions
    Code that consists within such construction is not checked.
  • FIXED: Handling long comments in VCX files
    In some cases there could bubble an error "variable not exists" when that was really a part of a long comment
  • IMPROVED: Analysis of functions that made up arrays such as adir(), alines() etc.
    In some cases there was possible an error of defining of indexes of object properties and object methods and parameters which have the same name as functions mentioned above.
    Example: this.aError[1,1]
  • NEW: Handling of new (in VFP 8.0) system variables.
    Using these variables now is no longer considered as an error: _codesense, _foxcode, _foxref, _foxtask, _getexpr, _incseek, _include, _objectbrowser, _pagetotal, _tasklist, _toolbox.
  • NEW: Main form of +CodeInspector can be minimized.
  • FIXED: Error while working under VFP 6.0 and checking classes from VFP 8.0
    (that were inherited from classes that have no definitions in VFP6)
  • IMPROVED: Installation structure.
    Since this version all support files of VFP are installed in the same folder with +CodeInspector, to avoid error "Cannot locate the Microsoft Visual FoxPro support library"

  • +CodeInspector 2.3

  • NEW: Processing of an explicit definition of type at the announcement of variables of type: " private cString as string"
  • NEW: Processing of an explicit definition of an array at the announcement of variables of type: " private array aString [1] "
  • NEW: The item "View Error" in the context menu of [+] button in the "Code Inspector main window" form.
  • FIXED: Recursive detour of section with the announcements of constants: #define CONSTANT_NAME CONSTANT_VALUE
  • FIXED: Removal of the registration data after new installation of the program
  • FIXED: Checking of system VFP variables (were case sensitive) such as: _MLINE ...
  • FIXED: The call of the help file from the "Code Inspector main window" form while option "set help off" is on.
  • FIXED: The version value in the "CodeInspector options" form (tab "+CodeInspector").
  • FIXED: Miscellaneous defects in the help.
  •