Hi Bjoern,
On Thu, 2012-06-14 at 12:02 +0200, Bjoern Michaelsen wrote:
> > [property] com::sun::star::lang::XComponent activeDocument;
>
> An even more radical approach would be assuming properties to just be a
> dynamic
> string->any map. Python allows mapping those to native attributes with:
The problem is - if you use a Java or C# binding that requires types,
and can provide intelligent auto-completion in the code (at least until
we hit an 'any' or 'queryInterface') - then using this overly-generic:
any doIt([in] any);
style interface for everything not only robs you of documentation and
auto-completion, but also means that you have to go lookup the types
carefully to make sure you don't shove an any into a string when it is
really an int (or whatever) and thus bust your run-time :-)
> letting the language bindings provide the syntactic sugar around
> that with reflection and stuff like python metaclasses(*). That
> would also mean:
So - syntactic sugar sounds good to me ;-) I'd particularly like a
built-in UNO, efficient signal/slot mechanism and native language
bindings for each language [ but particularly C++ ]. Native sugar for
our new "one stream interface" might be good too, to make streaming
intuitive.
Anyhow ;-) that's my take.
ATB,
Michael.
--
[email protected] <><, Pseudo Engineer, itinerant idiot
_______________________________________________
LibreOffice mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice
