Hi, Joachim Lingner <[EMAIL PROTECTED]> wrote: > > I also heard it was written using Managed C++. > Correct. > > So, this would not let > > it work with other CLI implementations, such as, Mono. > Yes, Mono does not work. > > C# would have > > been a better choice. > > Would anybody be willing to work on a C# version of UNO-CLI that could > > run on .NET and other CLI implementations, such as, Mono?
I'm looking at UNO-CLI wrt. Mono now. I don't have much UNO internals knowledge yet, but I know how to build OOo ;-), have written some patches for ooo-build and small C++ programs (and even smaller Python programs) that use UNO. If I read the code correctly, a pure C# version of UNO-CLI is not possible, because the bridge has to have C linkage. That code would somehow link to the runtime which is not portable at all (IIUC; my CLR knowledge is not that great either). > This would < > > allow it to work on Linux, Windows, Mac OS X, etc... > > That would be great. Good luck. If you'd rewrite UNO-CLI as portable as possible, where would you make the managed/native split? (I'm just trying to have you do my homework ;-) Thanks, Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
