This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Whole code is marked as error when only one word is incorrect | ||
---|---|---|---|
Product: | javafx | Reporter: | Alexandr Scherbatiy <sunflower> |
Component: | Editor | Assignee: | J Bachorik <yardus> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | ||
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Alexandr Scherbatiy
2008-09-26 12:39:30 UTC
This is in fact correct behaviour. Closing as invalid. Just compare it with Java: ------------- A.java ---------------- public class A { public void a() {}; public void b() {}; public abstract void c(); } ------------------------------------------ Only 'public class A {' line is marked as error. ------------- A.fx ---------------- public class A { public function a() {}; public function b() {}; public abstract function c() ; } ------------------------------------------ All code, even a and b functions are marked as error. This is low priority now compared to the other problems we have. Feel free to bump up the priority after we release 1.0. This is the way the javafxc reports errors. The only way to fix this would be getting the javafx compiler guys to fix the compiler. Please, create the compiler issue. Ok. It seems that it's not completely compiler's fault. After consulting the sources of java error highlighting I "adopted" the technique used there for checking the error highlighting position. Now the error marking is compatible with the one in java editor to a great extent. http://hg.netbeans.org/javafx/rev/50a203705f93 verified in marina-netbeans-plugin ยป #113 |