From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Stroesslin To: sourcenav@sources.redhat.com Subject: Re: Xref and find declaration of variables Date: Wed, 02 May 2001 04:33:00 -0000 Message-id: References: <3AEEF30F.6050805@link.com> X-SW-Source: 2001-q2/msg00125.html >I think you are asking the wrong question here. Naturally we >plan on fixing bugs in future releases. But the reality is >that we have to work on things as time permits. If you ok, I reformulate the question :-) "do you plan to fix the bug of not having proper scoping?" don't say it's not a bug, cause at least my first example must be considered a bug. do you agree on that, Mo? Ok, the others are feature whishes. But then again, Mo: end-user feedback is an important part of open source software development, don't you think? the order is: 1) release 2) user feedback 3) finetune, enhance, bugfix etc. where 2) and 3) are looped. I spoke about 2), not 3) to sourcenav users: I'd like to know if anybody else also misses the features I described. Maybe I am spoiled, but IMHO, it is very hard to analyse someone else's code without those features. And remember: 3) comes later; so don't let you be scared to silence if someone tells you immediately to code your whishes yourself if you're not happy. to Mo: If you really _are_ an opensource-man, please be nicer to end-users, as they help a lot on improving opensource software. >really need this feature fixes by a specific date, why >don't you roll up your sleeves and start hacking on the >source code? If you are uninterested in hacking on the >source code, you could always contract with Red Hat >to fix the problem. Heck, you could even hire a third >party to fix the problem and post a patch for inclusion >into the next release. You have plenty of options >when it comes to open source code. > >Mo DeJong >Red Hat Inc cheers, tom > Thomas Stroesslin wrote: > > >consider the following "project": > > > >myfile.c : > > > >int myglobalvar; > >int myfunc(int myarg) { > > int mylocalvar; > > int myvar; > > > > myvar = 1; > > mylocalvar = 1; > > myarg = 1; > > myglobalvar=1; > >} > > > >myotherfile.c : > > > >int myvar; // which is global > >... > > > >I am working on myfile.c and try to find out things about my variables: > > > >1) find declaration of myvar on the assignment line -> leads me to myvar > > of myotherfile.c (don't you have scope info in the db?) > > > >2) same as 1) for mylocalvar > > -> doesn't find anything, doesn't report error -> does nothing! > > > >3) same as 1) for myarg > > -> same as 2) > > > >4) myglobalvar referred by -> finds nothing > > > >5) myvar or mylocalvar or myarg referred by in function myfunc() > > -> same as 4 > > > > > >all these features are available in sniff+. IMHO, they are among the top > >10 most importand code analysis features (the other 5 are working in > >sourcenavigator, good stuff) > > > >do you plan to include such features in future releases of > >sourcenavigator? If so, when - roughly - can I expect them to be > >implemented? > > > >cheers, > >tom > > > > > > > -- --------------------------------------- Thomas Stroesslin DI-MANTRA (INF 130) EPFL CH-1015 Lausanne phone: +41 (0)21 693 52 64 E-Mail: mailto:thomas.stroesslin@epfl.ch WWW: http://diwww.epfl.ch/~stroessl/index.html PGP: http://pgp5.ai.mit.edu:11371/pks/lookup?op=get&search=0x183AA136