Stephan Bergmann wrote:
But if you create a new UNO runtime environment for Haskell (which should
be possible, for example using GHC's ccall) this would probably consist of more than just a bunch of UNO services.
Ok. Here's another thought. Haskell programs can be compiled. So, the only overhead in the package would be the Haskell<->UNO bindings. I wonder if that would be a significant overhead (both in file size and developer time).
Duplicating code into multiple UNO components sounds like a bad idea. When we ever come up with something useful to express dependencies of UNO components, we should remember that there are more kinds of dependencies than only UNO services (like, for example, specific UNO language bindings)...
-Stephan
I'll look into the GHC's ccall and find out what it is.
Cheers, Daniel.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
