Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » try without catch. A Bug?
try without catch. A Bug? [message #480838] Tue, 18 August 2009 15:52 Go to next message
Eclipse User
Originally posted by: kai.edinger.drexler-software.de

Hello,

i have a newbie question. I've found an try-finally construct in the
source org.eclipse.ui.views.markers.internal.ExtendedMarkersView (Method
getUpdateJob) from the org.eclipse.ui.ide plug-in.

The problem with it is, that an exception is raised if a translation is
incorrect (A incorrect format string). It produce a lots of
Error-Dialogs (once per minute ) without any stack-trace. So it is very
hard to find the incorret translation-string.

I've correct the translation-string at the babel project. But is this
also a bug in the source? Should it report this as bug?

Greeting
Kai
Re: try without catch. A Bug? [message #480856 is a reply to message #480838] Tue, 18 August 2009 17:16 Go to previous message
Paul Webster is currently offline Paul Webster
Messages: 6859
Registered: July 2009
Location: Ottawa
Senior Member

I would raise a bug to see if there is anything that can be done about continually opening dialogs ... it would be better if it didn't do that.

But try..finally is a java construct to ensure that code is executed (and it doesn't get in the way of the exception).

ex:
contexts.deferNotifications(true);
try {
// stuff
} finally {
contexts.deferNotifications(false);
}

This ensures that an exception from client code *cannot* put you in the state where you no longer send notifications.

PW


Previous Topic:Possible with commands?
Next Topic:Disable CVS menu Option
Goto Forum:
  


Current Time: Tue Oct 21 19:52:58 GMT 2014

Powered by FUDForum. Page generated in 0.02002 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software