Hi Thorsten,

>>  Referece< XFoo > xFoo( xFooSupp->getFoo(), UNO_SET_THROW );
> 
> I could live with that, too - only that I dislike the general
> direction of semantic overloading, instead of keeping things nicely
> separated (if they are orthogonal). Daniel's assertNonNull can be used
> at tons of other places, not only for this very specific use case.

Depends on the thrown exception - if it's special to this particular
case ...

Besides this: I'm for a balance between convenience and following the
higher ideals :)

As an example: Orthogonality was considered a Good Thing (TM) in UNO API
design for a long time. As a result, X*Container and friends are used in
many designs. Now over time, we realized that this might be a nice,
ideal design - but an inconvenient-to-use one. So now we encourage
people to use typed "XFoo getFooByIndex" designs, since this is easier
to use.

Similar, I don't consider "semantic overloading" a bad thing, if it
effectively saves hundreths of developers millions of characters to
type. That's a good trade, IMO.

Ciao
Frank

-- 
- Frank Schönheit, Software Engineer         [EMAIL PROTECTED] -
- Sun Microsystems                      http://www.sun.com/staroffice -
- OpenOffice.org Database                   http://dba.openoffice.org -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

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

Reply via email to