Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


Hello,

Sorry for this certainly naive and humble (because I wouldn't be able at all
to help here) question, but just by curiosity, is there some plan to rewrite
partly/clean UNO in order to:
- not depend on vtables implementation
- avoid to use of reinterpret_cast (and therefore possibly detect errors
during build)
- more generally make things clearer/simplify
- (multiple inheritance but do we want/need it?)
?

Of course I know that historical can have a huge impact so I would
understand easily there's no plan for the moment.

Julien



--
View this message in context: 
http://nabble.documentfoundation.org/I-need-to-better-understand-our-css-uno-Reference-tp4112779p4113340.html
Sent from the Dev mailing list archive at Nabble.com.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.