Issue 40814 - Make binary UNO more robust against missing type descriptions
Summary: Make binary UNO more robust against missing type descriptions
Status: ACCEPTED
Alias: None
Product: udk
Classification: Code
Component: code (show other issues)
Version: 680m70
Hardware: All All
: P4 Trivial (vote)
Target Milestone: AOO PleaseHelp
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-17 16:09 UTC by Stephan Bergmann
Modified: 2017-05-20 11:31 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Stephan Bergmann 2005-01-17 16:09:21 UTC
See issue 8581 for a stacktrace of a call to Any::operator <<= that crashes
because the type description for PropertyValue is missing.  Making this more
robust would mean to (a) add sal_Bool return values (or similar) to C functions
that can fail when type descriptions are missing (e.g., uno_type_any_assign),
and (b) let C++ functions throw RuntimeException when type descriptions are
missing (e.g., Any::operator <<=); both these changes would probably be
incompatible, however.
Comment 1 Stephan Bergmann 2005-01-17 16:10:26 UTC
accepted
Comment 2 Marcus 2017-05-20 11:31:41 UTC
Reset assigne to the default "issues@openoffice.apache.org".