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 Rainman,
After a period of time of developing with URE, I find the C++ UNO
class Reference is not very comfortable for use sometime.
The problem is, when I have a reference of base interface XA and a
reference of derived interface XB, I can't make xA = xB directly.
Instead I have to query
Thank you Frank,
you are right, get() is enough.
I haven't seen it before;)
On Wed, Mar 11, 2009 at 4:05 PM, Frank Schönheit - Sun Microsystems
Germany frank.schoenh...@sun.com wrote:
Hi Rainman,
After a period of time of developing with URE, I find the C++ UNO
class Reference is not very
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 Pradip,
better a late reply than never. :-)
Pradip Bhattacharya wrote:
Hi,
My name is Pradip Bhattacharya and I am working as a 3d mobile game engine
programmer. I have 3.6 years of experience in C,C++ and Java. I am very
happy with OpenOffice software as a replacement for other
Hey Frank,
I have another ideal, it is better and safer than the last one I mentioned.
I add a conversion operator to Reference, instead of a constructor, here is it:
template class base_interface_type
inline SAL_CALL operator const Reference base_interface_type ()
const
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
Hi Rainman,
I have another ideal, it is better and safer than the last one I mentioned.
I add a conversion operator to Reference, instead of a constructor, here is
it:
template class base_interface_type
inline SAL_CALL operator const Reference base_interface_type ()
const
Hi Frank,
No, I did not compile the OOo yet.
I have only recompile our product which was developed completely upon URE.
It seems that is compatible with existing code well.
On Wed, Mar 11, 2009 at 7:19 PM, Frank Schönheit - Sun Microsystems
Germany frank.schoenh...@sun.com wrote:
Hi Rainman,
I
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
On 03/11/09 12:19, Frank Schönheit - Sun Microsystems Germany wrote:
Admittedly, this feeling is not backed up by strong arguments, but I am
sure others could come up with some. Stephan?
Just keep it simple. ;)
-Stephan
-
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
*Hi,
so far we have got reported almost 40 regression as stopper for 3.1
release, see query
http://tinyurl.com slash cgsm3y .
for 3.0 ( **http://tinyurl.com slash ahkosf ) we had 27 of these issues,
for 2.4 (**http://tinyurl.com slash c86n3u** ) we had 23.
we are obviously getting worse
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
Frank Schönheit - Sun Microsystems Germany wrote:
Hi Rainman,
I have another ideal, it is better and safer than the last one I mentioned.
I add a conversion operator to Reference, instead of a constructor, here is it:
template class base_interface_type
inline SAL_CALL
Hi Andrew
I know that implicit conversions usually bring more side effects than
convenience. But it is not the reason that we should give all them up
I think ;)
There is no implicit conversion from std::string to const char*,
because if a string is destroyed, the pointer to its content will be
20 matches
Mail list logo
