To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=69706


User os changed the following:

                What    |Old value                 |New value
================================================================================
                Platform|Opteron/x86_64            |All
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Fri Jan 18 11:17:42 +0000 
2008 -------
The interface XNamed doesn't mention conflicts. It just requires the object's
name to be unique within the container. The documentation of
css::container::XNamed should be improved. 

>From my POV it is no acceptable solution to reinterprete the Name argument into
some arbitrary Name+<index> argument. The caller of a function must be able to
rely on the result of the operation. 
If I call setName("x") and the function doesn't throw then the object _must_ be
names "x" now. 

The user of this interface has to check the container if a name is already in 
use. 




---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to