Frank Schönheit - Sun Microsystems Germany wrote:
Not sure we need versioning, but we definitely need to way to
(carefully) break compatibility. As I've been told, this has been a
topic on this week's engineering steering committee meeting ...
I think we never will allow breaking
Frank Schönheit - Sun Microsystems Germany wrote:
Hi Rony,
*The former: it is just frustrating to have a program bomb and get a
message like exception occurred. (Yielding the message: go, figure...)*
which nicely fits into the original thread :)
Fixing those exceptions (which I
Hi Mathias,
However a reasonable error handling would look like, IMO carefully
re-designing UNO to add more exceptions specifications to (a lot of)
methods is a must-have.
+1
Just to play the devil's advocate: without careful considerations that
would end in adding throws
Hi,
On Wednesday, 2009-03-11 09:00:45 +0100, Frank Schönheit wrote:
OTOH designing exceptions right is very hard and often needs a lot of
thinking. So I don't expect that we can fix that in a big bang
release, we will need quite some time to fix that.
I would be happy if we would allow
Hi Eike,
OTOH designing exceptions right is very hard and often needs a lot of
thinking. So I don't expect that we can fix that in a big bang
release, we will need quite some time to fix that.
I would be happy if we would allow for such fixing. I don't want to fix
all of those at the same
On 03/11/09 11:43, Frank Schönheit - Sun Microsystems Germany wrote:
The only problem I see is that classes implementing the respective
interface need to be adjusted, too, which of course is error prone. If
this adjustment is not made, implementations throwing the new exception
might crash (at
Hi Stephan,
The only problem I see is that classes implementing the respective
interface need to be adjusted, too, which of course is error prone. If
this adjustment is not made, implementations throwing the new exception
might crash (at least on platforms where the compiler respects the
Frank Schönheit - Sun Microsystems Germany wrote:
Hi Stephan,
The only problem I see is that classes implementing the respective
interface need to be adjusted, too, which of course is error prone. If
this adjustment is not made, implementations throwing the new exception
might crash (at
On 03/11/09 15:12, rony wrote:
[Yes, I wholeheartedly agree, that the current situation is many
times frustrating, especially for beginners in an area of OOo (even
experts of one or two modules are beginners if turning to new
modules). There is a lot of resources that is being wasted just to
Stephan Bergmann wrote:
On 03/11/09 15:12, rony wrote:
[Yes, I wholeheartedly agree, that the current situation is many
times frustrating, especially for beginners in an area of OOo (even
experts of one or two modules are beginners if turning to new
modules). There is a lot of resources that
Stephan Bergmann wrote:
On 03/11/09 15:12, rony wrote:
[Yes, I wholeheartedly agree, that the current situation is many
times frustrating, especially for beginners in an area of OOo (even
experts of one or two modules are beginners if turning to new
modules). There is a lot of resources that
Hi Rony,
*The former: it is just frustrating to have a program bomb and get a
message like exception occurred. (Yielding the message: go, figure...)*
which nicely fits into the original thread :)
Fixing those exceptions (which I consider buggy in the current
messageless-shape) to carry a
12 matches
Mail list logo
