Pascal Analyzer 6.3.5 for Delphi versions D5 - XE5 » Developer.Team

Pascal Analyzer 6.3.5 for Delphi versions D5 - XE5

Pascal Analyzer 6.3.5 for Delphi versions D5 - XE5
Pascal Analyzer 6.3.5 for Delphi versions D5 - XE5 | 3.27 Mb


Pascal Analyzer (PAL), was released in 2001, and is currently in version 6. This program parses Delphi or Borland Pascal source code and produces reports that help you understand your source code better. You will also be able to identify potential errors and anomalies. Your code will be more readable and maintainable. Pascal Analyzer can also check how coding standard guidelines are followed. The static code analysis performed by Pascal Analyzer can help you find bugs early in the development process. According to a study published in 2002 by America's National Institute of Standards and Technology (NIST) software bugs cost to the American economy alone is $60 billion a year.

To summarize, Pascal Analyzer can:

Give faster time to market for new products
Improve application quality and reliability
Reduce overall cost of development, support, and maintenance

Version 6.3.5 October 29, 2013

fixed error parsing asm statement in some cases
fixed error when conditional expression spanned over more than one line
line numbers shown for syntax error are now absolute (not adjusted for included files)
better error message when file in uses statement has unsupported format (USC2 and others)
improved handling of environment variables
fixed error parsing helper class
fixed error parsing "unsafe" directive
wrong value for when unicode identifiers were first allowed, was set to D2007, but is D2005
improved resolving references to identifiers with same name
fixed error parsing property declaration
unit scopes were not reported in Status Report for targets higher than XE2
improved handling of function results
conditional directive "EXTERNALLINKER" was not registered
when reading older Delphi project files, each setting was truncated if having more than 2048 characters
call to "Release" was registered for class object, even if field with the same name existed
created misformed XML for Uses Report in some situations
predefined identifiers for XE4 were not loaded properly

Home:
http://www.peganza.com/#PAL


Direct Mirror for V.I.P