| Re: [cdt-dev] Indexer polluting the log file |
|
We could log the exception every time there is a unresolved symbol. Or we can summarize it into a single log entry as we are doing now, maybe only logging it when there are unresolved symbols or other problems.
From: Cortell John-RAT042 <RAT042@xxxxxxxxxxxxx>
Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx> Date: Friday, 24 August, 2012 9:18 AM To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx> Subject: Re: [cdt-dev] Indexer polluting the log file I'm sorry, but I have to respond to this one. This all makes perfect sense, but the crux of the matter lies in your last sentence.
"...option should be on per default in order to serve people that report problems."
Again, there is no shortage of problems that can occur in Eclipse. This rationale does not scale well. The log file would be jam packed with trace information if other feature developers took the same position. Perhaps, though, you would see that as acceptable.
I suppose it's a matter of perspective on the role of the log file. What I am certain of is that, by and large, Eclipse project plug-in developers take the perspective that it's for error reporting and not tracing, certainly not tracing that's on by default.
John
From:
cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Schorn, Markus [Markus.Schorn@xxxxxxxxxxxxx]
Sent: Friday, August 24, 2012 3:52 AM To: CDT General developers list. Subject: Re: [cdt-dev] Indexer polluting the log file Hi, The information in the log is helpful for two things: · It provides you feedback about the quality of the indexing and you do not have another way of getting this kind of information. · When an index related issue (navigation, semantic highlighting, …) is reported you have a quick way of figuring out whether the reporter has a reasonable indexer setup. Reporters are usually willing to provide their log, less often they will do a tracing for you.
I never thought of the log as something that has to be meaningful to the end user, rather than that for me it is a facility to collect information that can help in resolving issues once they have occurred. The information is put into the log as information (which can be filtered away) and it is only written, when the index is rebuilt from scratch (which should not happen too often). It may be worth looking into why the information is written that often (is the index rebuilt that often?)
Obviously writing the information to the log can be made optional. But then again the option should be on per default in order to serve people that report problems.
Markus.
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Alex Blewitt
This should really be configurable and disabled by default. Filling the log with cruft doesn't help anyone who is looking after Eclipse users and want to debug different problems where CDT may also be involved.
If it's really necessary to know whether an indexer has not run, maybe logging when it fails is more appropriate. But there's a debug options setup that allows you to increase the level of verbosity of particular features - it sounds like that should be used instead of all the time.
Alex
|