From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mo DeJong To: sourcenav@sourceware.cygnus.com Subject: Re: Java hiccups Date: Mon, 15 Jan 2001 16:32:00 -0000 Message-id: References: <20010106155656.14818.qmail@nwcst338.netaddress.usa.net> X-SW-Source: 2001-q1/msg00020.html On 6 Jan 2001, h j wrote: > Hi, > I am trying this program for a large java project. It is the most stable, fast > and useful product, even compared to some commercial ones. > > But it seems that java is not fully supported as yet. Firstly, there is an > important bug: The program does not recognize "java.awt.Component" as > "Component" from the "java.awt" package. It seems like the package concept is > not there at all. You are correct. We need to fix the Java parser so that it understands Java packages. > Also, the program has an irritating habit of distinguishing a method > definition and declaration. In java there is no such distinction, but source > navigator shows two entries for each method! This is a known problem. This sort of thing could also come up in C++ in the case of an inlined method. The question is, what is the right way to fix this? Should only a single type symbol be written, for example we could leave off the decl symbol. The problem is, we then need to do something when the user ran "Goto decl". > What is the status for java support ? Is there a chance of these > issues being fixed in the near future ? We are talking about the "right" way to fix it but it is going to require some work. The GCJ based parser would work for Java code that would compile, but fuzzy Java parsing is a much harder problem. Mo DeJong Red Hat Inc