ISAC: new IRS 2051 and 2052

It look like I forgot to send these out.
Chuck Swart

-------------BEGINNING OF IR----------------

VHDL Issue Number: 2051

Language_Version: VHDL-2002
Classification: Language Definition Problem
Summary: path_name and instance_name do not allow for protected types
Relevant_LRM_Sections: 14.1
Related_Issues:
Key_Words_and_Phrases: protected type, path_name, instance_name, attribute
Authors_Name: Peter Ashenden
Authors_Phone_Number: +61 8 8339 7532
Authors_Fax_Number:
Authors_Email_Address: peter@ashenden.com.au
Authors_Affiliation: Ashenden Designs
Authors_Address1:
Authors_Address2:
Authors_Address3:

Current Status: Submitted

Superseded By:

------------------------
Date Submitted: 28 January 2004
Date Analyzed:
Author of Analysis:
Revision Number: 0
Date Last Revised:

Description of Problem
----------------------

 The rules for the path_name and instance_name attributes do not
 describe how to form a package based path, a path to instance or a
 full path to instance for a named entity declared with a protected
 type.

Proposed Resolution
-------------------

 In the rules for path_instance_element and
 full_path_instance_element, add shared_variable_simple_name as an
 alternative.

    Change the rule for package_based_path to
    
    package_based_path ::=
      leader library_logical_name leader
      [ package_simple_name leader ]
      { package_path_element leader }
      [ local_item_name ]
    
    package_path_instance_element ::=
        subprogram_simple_name signature
      | protected_type_simple_name
    
    
VASG-ISAC Analysis & Rationale
------------------------------
TBD

VASG-ISAC Recommendation for IEEE Std 1076-1993
-----------------------------------------------
TBD

VASG-ISAC Recommendation for Future Revisions
---------------------------------------------
TBD

-------------END OF IR----------------

-------------BEGINNING OF IR----------------

VHDL Issue Number: 2052

Language_Version: VHDL-2002
Classification: Language Modeling Enhancement or Deficiency
Summary: path_name and instance_name don't deal with operator symbols
Relevant_LRM_Sections: 14.1
Related_Issues:
Key_Words_and_Phrases: path name, instance name, attribute, subprogram
Authors_Name: Peter Ashenden
Authors_Phone_Number: +61 (8) 8339 7532
Authors_Fax_Number:
Authors_Email_Address: peter@ashenden.com.au
Authors_Affiliation:
Authors_Address1:
Authors_Address2:
Authors_Address3:

Current Status: submitted

Superseded By:

------------------------
Date Submitted: 28 January 2004
Date Analyzed:
Author of Analysis:
Revision Number: 0
Date Last Revised:

Description of Problem
----------------------

 The definitions of the path_name and instance_name attributes refer
 to subprogram_simple_name. However, a simple_name is just an
 identifier, and does not cover operator symbols. The implication is
 that a path_name or instance_name attribute of a named entity
 declared within subprogram that overloads an operator is not defined.

Proposed Resolution
-------------------

 In each of the full_path_instance_element and path_instance_element
 productions, add an alternative of the form

    
      subprogram_operator_symbol signature
    

VASG-ISAC Analysis & Rationale
------------------------------
TBD

VASG-ISAC Recommendation for IEEE Std 1076-1993
-----------------------------------------------
TBD

VASG-ISAC Recommendation for Future Revisions
---------------------------------------------
TBD

-------------END OF IR----------------
Received on Mon Dec 20 10:54:32 2004