This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 401484 - otype references false positive warnings
Summary: otype references false positive warnings
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: VJET (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Justin Early CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-21 20:48 EST by Justin Early CLA
Modified: 2017-04-11 15:12 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Justin Early CLA 2013-02-21 20:48:25 EST
In vjojs  you can define an otype in a nested class meta type 

vjo.ctype('funcs.TL1') //< public 
.props({
	//> public
	func: vjo.otype().defs({ 		
		
		errcb: vjo.NEEDS_IMPL	//< public void errcb(Error err); some docs here
	}).endType(),
	
	//> public
	data: vjo.otype().defs({
		// *** BUG: this should appear as "public" in the outline/members views
		options: {		//< public
			fd: null,  	//< public int
			name: null 	//< public String?
		}
	}).endType()
})
.protos({
	//aaa: vjo.NEEDS_IMPL, //< public int aaa( (void f(Error err)) cb )
	

	// We have to be able to refer to an otypes function as a "ref"
	bbb: vjo.NEEDS_IMPL, //< public int bbb(TL1.func:errc cb); warning expected typo case
	ccc: vjo.NEEDS_IMPL, //< public int bbb(TL1.func:errcb cb); no warning expected
	
	ccc1: vjo.NEEDS_IMPL, //< public void ccc(TL1.data:options opts); no warning expected 
	ccc2: vjo.NEEDS_IMPL //< public void ccc(TL1.data:optons opts); expect warning typo case
})
.options({
	
	metatype: true
})
.endType();
Comment 1 Justin Early CLA 2013-02-21 20:50:08 EST
fixed in nightly