PR# 18047 Two VFAC(1) errors reported for redefinition with nonexistent assigner command
Problem Report Summary
Submitter: prestoat2000
Category: Compiler
Priority: Medium
Date: 2011/12/12
Class: Bug
Severity: Non-critical
Number: 18047
Release: 7.0.88074
Confidential: No
Status: Closed
Responsible:
Environment: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.9.0.10) Gecko/2009042715 Firefox/3.0.10
Solaris 10
Synopsis: Two VFAC(1) errors reported for redefinition with nonexistent assigner command
Description
Redefining a feature with an assigner command, where the redefinition names
a nonexistent assigner command, causes the compiler to report two VFAC(1)
errors instead of one.
Looks like the problem is that {FEATURE_I}.is_same_assigner has a side
effect of inserting a VFAC(1) error, which seems like a bad idea, and
appears to be unnecessary. The fix may be as simple as not reporting
VFAC(1) in that routine, though you will need to check the other caller(s)
to see if they still behave correctly.
Added test valid274 for this bug.
To Reproduce
Run test valid274.