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

Bug 363517

Summary: Private functions should not be allowed to be assigned as a value
Product: z_Archived Reporter: Paul Harmon <pharmon>
Component: EDTAssignee: Project Inbox <edt.compiler-inbox>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3 CC: jspadea, svihovec
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Limit usage of private functions none

Description Paul Harmon CLA 2011-11-10 13:48:06 EST 
Validation needs to prevent private functions from being assigned to delegates, so prevent private functions from being invoked outside of a given Part.

The validation required is that a private function is not valid for use:

1) as the RHS of an assignment statement
2) as the source of a move
3) as a function argument
4) as the value of a return statement
Comment 1 Paul Harmon CLA 2011-11-16 15:54:09 EST 
This is still needed, but we are deferring it out of .7
Comment 2 Justin Spadea CLA 2012-07-06 16:05:24 EDT 
Created attachment 218401 [details]
Limit usage of private functions
Comment 3 Justin Spadea CLA 2012-07-11 10:45:06 EDT 
FYI this change is going to introduce a lot of validation errors once introduced. The RUI widgets and Dojo widgets have 38 errors with this change, and that's not including the mobile widgets. We can fix them in newer widget projects but existing workspaces will suddenly be unusable without manually updating the widgets.
Comment 4 Justin Spadea CLA 2012-11-28 09:28:35 EST 
Taking myself off as the owner; we might end up not doing anything about this given how it'll break so many applications.
Comment 5 Matt Heitz CLA 2013-01-03 14:01:39 EST 
Deferring to Future.  This won't be done in 0.8.2.