Re: The XServiceInfo interface ...

[Maciej Stachowiak <mjs eazel com>]

Michael Hoennig "(mi)" <mi sun com> writes:

> 
> why 'X', I don't know anymore. Microsoft started with 'I' and somehow we 
> chose 'X' to be different. And yes, ALL an ONLY our code generating 
> interfaces start with this prefix. Or what do you mean? Although UNO has 
> runtime code generation anyway. But that's a different story.

`X' is comment as an abbreviation for `inter' or `trans', perhaps
because of the crossing effect, thus (seen in various places) `XF' for
"InterFace", `xcvr' for "transceiver", etc.

> >         So, these names are in a different namespace then, oh well. 
> 
> For the implementation yes, but it makes documentation generation a lot 
> easier, of names cannot clash even for services vs. interfaces: We just 
> create files like "com/sun/star/text/XTextField.html" and 
> "com/sun/star/text/TextField.html" for example. And all automatically 
> generated links (from syntactical information) are very straight forward. 
> If both were "TextField", we had a problem here.

I suggest it might be cleaner to prefix the service names if anything,
since the actual interface names will be used in code a lot more. Or
put them in a sub-module:

OpenOffice::Foobar

OpenOffice::Service::Foobar

Prefixing is silly when you have namespaces.

 - Maciej