Release Notes - 1.0

PL1 1.0.6

Resolved issues

PL1 1.0.5

Updates

• Strings are now processed as strings
• Nested PLI/PLCFunctions/Procedures are now detected correctly
• ++include and -inc syntaxes are now supported
• Column numbers are now disregarded when PLI/PLCFunctions/Procedures are saved as objects, therefore object names no longer contain this information
• Code depth detection is improved significantly in PL 1.0.5 resulting in lesser warnings of type “unable to find object end for ”.

Impacts of upgrading to this version

During the source code pre-processing phase that is done as part of the delivery and analysis process, CAST will now add “$$” to all PL1 source code just prior to the “;”. For example:

Original source code

someproc:proc;

Source code after pre-processing in < 1.0.5

someproc:proc;

Source code after pre-processing in ≥ 1.0.5

someproc:proc$$;

The impact of this change is as follows:

• Existing objects will be shown as updated when a post upgrade snapshot is run.
• There will be a reduction in the number of messages of the type “end of object of type <PLC\PLIProcedure|Function> not found” that were previously displayed in the log.

This change has been implemented because of a limitation in the CAST analyzer with regard to the way object start and end patterns are handled. In PL1, object start and end patterns do not match (contrary to most other languages, such as PHP where { and } are used) and therefore the analyzer is not able to correctly identify when an object ends.

Resolved issues

SQL query for Oracle environments:

begin
    update ctt_object_applications app_objects 
    set app_objects.properties = 2 where app_objects.object_id in (
      select objects.object_id from cdt_objects objects, DSSAPP_MODULES modules
      where modules.MODULE_ID = app_objects.application_id
      and regexp_like(objects.object_fullname, '\\UNKNOWN\\' || objects.OBJECT_NAME || '.PLI.PLIMainProcedure.' || objects.OBJECT_NAME || '$')
    );
    COMMIT;
 end;

PL1 1.0.4

Updates

In this release the Quality Rule Avoid using letters as I, J, K,.. for loops instead of using more meaningful variables (PL1) - 1001076 has been removed. As a direct result of this:

• The associated metric “PLI: Use of I J K in Loop” has also been removed.
• The associated metamodel type “PLIProcDOVar (PLI DO Variable)” has been marked as deprecated
• The associated Quality Rule stored procedure “PL1_PLIPROC_PP102” has been removed:
  • On CAST AIP schemas installed on CAST Storage Service, after upgrading from PL1 ≤1.0.3 the stored procedure will no longer exist
  • On CAST AIP schemas installed on Oracle Server, after upgrading from PL1 ≤1.0.3 the stored procedure will remain in place but no longer be used
• The impacts on analysis results of this decision are as follows:
  • No objects of type PLIProcDOVar (PLI DO Variable) will be resolved and saved in the CAST Analysis Service schema
  • The analysis log will no longer contain “duplicate object” warnings for PLIProcDOVar (PLI DO Variable) objects.
  • After upgrading from PL1 ≤1.0.3 with existing snapshots, the Quality Rule will no longer be visible in the CAST dashboards for all existing snapshots and any new snapshots (that are generated with PL1 ≥1.0.4)
• The entry in the CAST Delivery Manager Tool for packaging PL1 source code has been renamed “PL1”. In addition, it has been moved from the “Source Code Management” section to the “Repository” section.

Resolved issues

PL1 1.0.3

Resolved issues

PL1 1.0.2

Resolved issues

PL1 1.0.2 contains various fixes for issues found preventing compatibility with CAST AIP 7.3.3.

PL1 1.0.1

Resolved issues

PL1 1.0.0

Updates

• The Regular Expression engine used to interpret the Regular Expressions defined in the Quality Rule configuration has changed. BOOST is now used in place of TCL. Please see http://www.boost.org/doc/libs/1_52_0/libs/regex/doc/html/boost_regex/syntax/perl_syntax.html  for more information about BOOST
• In this release, the manual preprocessing step is no longer required - it is actioned automatically during code source Delivery via the CAST Delivery Manager Tool.