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.
Parser fails on this code (it is C code): ------------------------------------ i = 6; int main() { return 0; } ------------------------------------ vs157455@ifdefqe-02:~/ifdef_testbase/test-performance/nb_all/performance/test/tracemodel> ./tracemodel.sh ~/Application1/newfile.c Java: /usr/bin/java java version "1.5.0_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08) Java HotSpot(TM) Client VM (build 1.5.0_01-b08, mixed mode, sharing) newfile.c:2:1: unexpected token: j newfile.c:2:5: expecting EOF, found '6'
Though the construct in the example is correct, this is an *extremely* rare case. And this is a *very* bad style of code. I don't believe it's used any more. I'm not saying we shouldn't fix it. But isn't that serious to be a P2.
Have you ever declared a variable with no type? I bet you don't. Have you ever seen such a variable? Well, if a developer sees such a variable in the code (s)he maintains, what should (s)he do? Yes, immediately change it to the explicit "int". What's the value of this issue then? I strongly believe it's a P4.
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. We apologize for any inconvenience. Thank you. The NetBeans Team