[doob]

I'm not sure if this is a bug or if descent isn't "good enough" yet but often descent doesn't show all the errors it should show. Example, I'm porting a Java project to D and almost the only error descent shows is that name of the constructor is wrong:

module dwt.internal.cocoa.NSEnumerator;

import dwt.dwthelper.utils;

public class NSEnumerator : NSObject {

public NSEnumerator() {
super();
}

public NSEnumerator(objc.id id) {
super(id);
}

public NSArray allObjects() {
objc.id result = OS.objc_msgSend(this.id, OS.sel_allObjects);
return result !is null ? new NSArray(result) : null;
}

public id nextObject() {
objc.id result = OS.objc_msgSend(this.id, OS.sel_nextObject);
return result !is null ? new id(result) : null;
}

}

The text that is bold is where descent shows me errors. If I change the constructor to the proper name "this" than descent doesn't show me any errors at all even thought it should. Descent should show that it can't find the types "OS", "NSObject" and "NSArray" and that it's something wrong with "objc.id" because I haven't imported them yet.

[asterite]

I'll disable the "show semantic errors" feature because until now I didn't succeeded to get this OK without sacrificing performance. It's really an experimental feature, sorry.