View previous topic :: View next topic |
Author |
Message |
asterite
Joined: 01 Jun 2006 Posts: 235 Location: Buenos Aires, Argentina
|
Posted: Mon Sep 03, 2007 12:02 pm Post subject: |
|
|
Why you can't debug? Do you still get the ClassNotFoundExceptin: descent.internal.ui.wizards.JavaProjectWizard? |
|
Back to top |
|
|
L
Joined: 01 Sep 2007 Posts: 21 Location: Germany
|
Posted: Mon Sep 03, 2007 12:38 pm Post subject: |
|
|
Yes. I even made a new copy of all decent* projects from svn. Then I checked all settings, you mentioned in the previous posts. But eclipse still hates me...
Perhaps I should check my ubuntu installation.... |
|
Back to top |
|
|
asterite
Joined: 01 Jun 2006 Posts: 235 Location: Buenos Aires, Argentina
|
Posted: Mon Sep 03, 2007 12:41 pm Post subject: |
|
|
What I did was to make sure java -version gave me the same version used by Eclipse. Then in Windows -> Prefereces -> Java -> Compiler I selected 5.0 compliance. Then I cleaned up all the projects and built them all.
What you can do is to export the descent.launching plugin (open plugin.xml and select Export), copy it over your previous one, and see if now it works well. If it does, I'll release. |
|
Back to top |
|
|
L
Joined: 01 Sep 2007 Posts: 21 Location: Germany
|
Posted: Mon Sep 03, 2007 4:19 pm Post subject: |
|
|
Sorry, it took a bit longer because of a BBQ...
I've compiled and exported the plugin, but I get this error. Let's see why...
java.lang.StackOverflowError
at descent.internal.compiler.parser.Type.getProperty(Type.java:617)
at descent.internal.compiler.parser.Type.getProperty(Type.java:610)
at descent.internal.compiler.parser.Type.dotExp(Type.java:722)
at descent.internal.compiler.parser.DotIdExp.semantic(DotIdExp.java:208)
at descent.internal.compiler.parser.UnaExp.semantic(UnaExp.java:103)
at descent.internal.compiler.parser.CallExp.semantic(CallExp.java:156)
at descent.internal.compiler.parser.CallExp.semantic(CallExp.java:206)
at descent.internal.compiler.parser.CallExp.semantic(CallExp.java:206)
at descent.internal.compiler.parser.CallExp.semantic(CallExp.java:206)
at descent.internal.compiler.parser.CallExp.semantic(CallExp.java:206)
at descent.internal.compiler.parser.CallExp.semantic(CallExp.java:206)
at descent.internal.compiler.parser.CallExp.semantic(CallExp.java:206)
at descent.internal.compiler.parser.CallExp.semantic(CallExp.java:206)
... |
|
Back to top |
|
|
L
Joined: 01 Sep 2007 Posts: 21 Location: Germany
|
Posted: Mon Sep 03, 2007 5:55 pm Post subject: |
|
|
The error occurs after creating a new D-project with standard settings, adding a new module and typing in the following stuff. After completing "writefln(" I got the stack overflow.
module pack1.mainmod1;
import std.stdio;
int main(char[][] args){
writefln()
} |
|
Back to top |
|
|
asterite
Joined: 01 Jun 2006 Posts: 235 Location: Buenos Aires, Argentina
|
Posted: Mon Sep 03, 2007 7:48 pm Post subject: |
|
|
Sorry, I forgot to tell you something. The SVN trunk has enabled the partial semantic analysis that has been ported. For example, try writing this:
int foo() {
}
You'll get an error in "foo" saying that "foo" is missing a return type. Change it to:
int foo() {
return "hey!";
}
and you'll get an error saying "hey!" cannot be implicitly converted to int.
For some other stuff, though, since the porting is not finished, you'll get errors. To disable the semantic analysis, go to the class descent.core.dom.CompilationUnitResolver and set the RESOLVE flag to false. Now you'll only get syntax errors reported (and no StackOverflow or NullPointer exception ).
Be sure to export the plugin with the flag set to false. |
|
Back to top |
|
|
asterite
Joined: 01 Jun 2006 Posts: 235 Location: Buenos Aires, Argentina
|
Posted: Mon Sep 03, 2007 7:49 pm Post subject: |
|
|
* that foo must return a result of type int (instead of "it's missing a return type") |
|
Back to top |
|
|
L
Joined: 01 Sep 2007 Posts: 21 Location: Germany
|
Posted: Thu Sep 06, 2007 12:42 pm Post subject: |
|
|
Damn, 20:40 and still at work...
In my last test, I got this stack overflow, and the debugging still did not work. Should I try to build the new version from svn? Have you made any progress with it or is your current goal to implement this neat semantic analysis? |
|
Back to top |
|
|
asterite
Joined: 01 Jun 2006 Posts: 235 Location: Buenos Aires, Argentina
|
Posted: Thu Sep 06, 2007 1:02 pm Post subject: |
|
|
Supposedly I've fixed the debugging problem. Get the latest version from SVN and compile. Also make sure the RESOLVE flag in CompilationUnitResolver is false. With this, you shouldn't get the stack overflow. Have you turned that flag to false??? |
|
Back to top |
|
|
L
Joined: 01 Sep 2007 Posts: 21 Location: Germany
|
Posted: Sun Sep 09, 2007 8:30 am Post subject: |
|
|
Funny. I've downloaded eclipse Europa and now I can compile your plugin and debug it. Which eclipse version do you use normally? And which eclipse version have you used in your ubuntu-vm-installation? If it was eclipse Europa (v. 3.3.something), this could be one of the prerequisites to use your svn-project properly. |
|
Back to top |
|
|
asterite
Joined: 01 Jun 2006 Posts: 235 Location: Buenos Aires, Argentina
|
Posted: Sun Sep 09, 2007 8:44 am Post subject: |
|
|
I normally use Eclipse 3.2, because I know not everyone has Europa yet, so I don't want to depend on it... This is all very strange... |
|
Back to top |
|
|
L
Joined: 01 Sep 2007 Posts: 21 Location: Germany
|
Posted: Mon Sep 10, 2007 7:03 am Post subject: |
|
|
Btw: Nope, the debugging stuff still does not work. Perhaps you could explain, where I can start, so that I can help implementing some stuff. |
|
Back to top |
|
|
|