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

Bug 318993

Summary: [debug] private role method bridge is interpreted as callin wrapper
Product: [Tools] Objectteams Reporter: Stephan Herrmann <stephan.herrmann>
Component: OTDTAssignee: Stephan Herrmann <stephan.herrmann>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: 0.7   
Target Milestone: 0.7.1   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
implementation none

Description Stephan Herrmann CLA 2010-07-06 07:48:10 EDT
When stepping into a bridge for a private role method, this bridge
is beautified in the Debug view like a callin wrapper, so using
Team1122lt8_2 (from TeamNesting tests), and using a BP on R2#k->k
and then hitting F5 we see:
  Team1122lt8_1$R1.[R1.private<-k](int, Team1122lt8_1, Team1122lt8_1$R1) line: 7
  Team1122lt8_1.[R1.private<-k]() line: 7	
  Team1122lt8_2$R2.k() line: 11	
The first 2 frames are colored green.

Instead they should be colored pale-purple and say something like
"accessing private method k()"

Also: how about using STEP-INTO linenumber for these?
Comment 1 Stephan Herrmann CLA 2010-09-04 14:43:11 EDT
Created attachment 178213 [details]
implementation

This patch beatifies a number of different access methods:
 - _OT$create$R : accessor for role constructor
 - _OT$InitFields: field initializations extracted from constructors
 - _OT$decaps$xy : decapsulation access
 - _OT$R$private$m: callout access to private role method
Comment 2 Stephan Herrmann CLA 2010-09-04 14:44:13 EDT
Patch has been committed as r759
Comment 3 Stephan Herrmann CLA 2010-09-23 13:42:54 EDT
Verified using I201009211735