Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 321545

Summary: evaluation of implicit 'unit' results in evaluation of unit's name as variable
Product: z_Archived Reporter: Henrik Lindberg <henrik.lindberg>
Component: b3Assignee: Project Inbox <b3.engine-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Henrik Lindberg CLA 2010-08-02 23:39:38 EDT 

    


    


      



        
          Comment 1
        

        
          Henrik Lindberg CLA

        

        
        

        
          2010-08-02 23:42:01 EDT
        

      






When a reference is made to the variable 'unit' in a builder with implicit unit paramater (i.e. a builder defined in a unit), the evaluation of the variable reference ends up using the name of the unit as the name of the variable!

When a builder is advised, the unit parameter is explicit, and there is no as the INamedValue is indeed named 'unit'.

    


    


      



        
          Comment 2
        

        
          Henrik Lindberg CLA

        

        
        

        
          2010-08-02 23:44:35 EDT
        

      






Fixed in rev 1242.

The fix consists of introduction of an extra interface IVarName that a INamedValue can implement if it wants to be called something else than its intrinsic name.

A BuildUnit that is referenced via variables is now always called "unit", and scope determines which unit this is.