Are there any currently maintained tools for interfacing Haskell with COM objects? It appears that both Haskell script and Haskell direct haven't been updated since the turn of the century, and have fallen out of step with recent library changes.
Hello Darrell,
On Tue, 26 Jun 2007 03:08:02 +0900, Lewis-Sandy, Darrell
Are there any currently maintained tools for interfacing Haskell with COM objects? It appears that both Haskell script and Haskell direct haven't been updated since the turn of the century, and have fallen out of step with recent library changes.
You can download latest version of H/Direct from CVS, or hscom that is forked version of H/Direct's comlib from darcs. http://www.haskell.org/pipermail/libraries/2007-January/006737.html hscom breaks compatibility from H/Direct. Because developpers edit hscom by hand instead of to change generating code. So you must check and choice which is better to use your project. -- shelarcy <shelarcy hotmail.co.jp> http://page.freett.com/shelarcy/
The biggest Haskell/COM project I know of was Krasimir's implementation of Visual Haskell, which was a plug-in for Visual Studio. The VS interfaces are COM ones, so he had to do lots of COM stuff. He may be able to help you. Sigbjorn Finne knows a lot about HDirect, but he's really busy with his day job at Galois! There's a bit of a chicken-and-egg problem here; the COM tools are not well maintained, so that discourages use, which in turn makes it less rewarding to work on them. What I don't know is the level of suppressed demand: if there were good tools, would lots of people start using them? Simon From: haskell-cafe-bounces@haskell.org [mailto:haskell-cafe-bounces@haskell.org] On Behalf Of Lewis-Sandy, Darrell Sent: 25 June 2007 19:08 To: haskell-cafe@haskell.org Subject: [Haskell-cafe] Tools for Haskell and COM Are there any currently maintained tools for interfacing Haskell with COM objects? It appears that both Haskell script and Haskell direct haven't been updated since the turn of the century, and have fallen out of step with recent library changes.
From: haskell-cafe-bounces@haskell.org [mailto:haskell-cafe-bounces@haskell.org] On Behalf Of Simon Peyton-Jones
There's a bit of a chicken-and-egg problem here; the COM tools are not well maintained, so that discourages use, which in turn makes it less rewarding to work on them. What I don't know is the level of suppressed demand: if there were good tools, would lots of people start using them?
Um, well, yes, I demand. I want to interface Takusen with MS Sql Server, but AFAICT the recommended C API is OLE DB, which is a COM API. Not knowing COM at all, I assume I could program against it like a C programmer would, using just the FFI, but I imagine it will be easier to use a COM tool. Alistair ***************************************************************** Confidentiality Note: The information contained in this message, and any attachments, may contain confidential and/or privileged material. It is intended solely for the person(s) or entity to which it is addressed. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. *****************************************************************
Alistair Bayley wrote:
I want to interface Takusen with MS Sql Server, but AFAICT the recommended C API is OLE DB, which is a COM API.
An alternative would be to write a takusen <-> freetds binding (http://www.freetds.org/). This would have the potential benefits of being * cross platform (ie windows and linux) * multi db (ie ms-sql and sybase) I should admit that there's a bit of self-interest here... I'd use such a binding it it existed. Tim
From: Tim Docker [mailto:timd@macquarie.com.au]
Alistair Bayley wrote:
I want to interface Takusen with MS Sql Server, but AFAICT the recommended C API is OLE DB, which is a COM API.
An alternative would be to write a takusen <-> freetds binding (http://www.freetds.org/). This would have the potential benefits of being
* cross platform (ie windows and linux) * multi db (ie ms-sql and sybase)
I should admit that there's a bit of self-interest here... I'd use such a binding it it existed.
Interesting. I did not know that existed. A while ago I started working on a native MS Sql Server backend using db-lib, but then I read that db-lib was no longer maintained, and the OLE DB library was the recommended low-level API. It looks as though I could switch over to freetds, keep most of the db-lib code I've already written, and provide a back-end that works with Sybase too. This seems more appealing than learning how to do COM programming :-) Apologies to Simon-PJ: it seems my demand for better COM tools has just evaporated. Alistair ***************************************************************** Confidentiality Note: The information contained in this message, and any attachments, may contain confidential and/or privileged material. It is intended solely for the person(s) or entity to which it is addressed. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. *****************************************************************
There's a bit of a chicken-and-egg problem here; the COM tools are not well maintained, so that discourages use, which in turn makes it less rewarding to work on them. What I don't know is the level of suppressed demand: if there were good tools, would lots of people start using them?
I think it will be beneficial for many Windows user if there was a good Haskell to COM integration. HDirect can be a real nightmare for a large projects. The first step could be to build a new COM library designed in more FFI addendum fashion. I already have started the first step with: http://darcs.haskell.org/packages/hscom/ It is far from complete of course. The second step should be to reimplement the IDL->Haskell translator. The existing translator often generate code that isn't type correct and even if you change the code by hand there is still a chance to have an implementation errors which can't be captured from the typechecker. The whole task isn't that hard but still requires a volunteer willing to spend 2-3 months of full time work. Regards, Krasimir
Simon Peyton-Jones wrote:
The biggest Haskell/COM project I know of was Krasimir’s implementation of Visual Haskell, which was a plug-in for Visual Studio. The VS interfaces are COM ones, so he had to do lots of COM stuff. He may be able to help you. Sigbjorn Finne knows a lot about HDirect, but he’s really busy with his day job at Galois!
There’s a bit of a chicken-and-egg problem here; the COM tools are not well maintained, so that discourages use, which in turn makes it less rewarding to work on them. What I don’t know is the level of suppressed demand: if there were good tools, would lots of people start using them?
Simon
Is now a bad time to say "what is COM?"?
Microsoft's Component Object Model.
http://en.wikipedia.org/wiki/Component_Object_Model
/g
On 6/27/07, Andrew Coppin
Simon Peyton-Jones wrote:
The biggest Haskell/COM project I know of was Krasimir's implementation of Visual Haskell, which was a plug-in for Visual Studio. The VS interfaces are COM ones, so he had to do lots of COM stuff. He may be able to help you. Sigbjorn Finne knows a lot about HDirect, but he's really busy with his day job at Galois!
There's a bit of a chicken-and-egg problem here; the COM tools are not well maintained, so that discourages use, which in turn makes it less rewarding to work on them. What I don't know is the level of suppressed demand: if there were good tools, would lots of people start using them?
Simon
Is now a bad time to say "what is COM?"?
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
-- The man who'd introduced them didn't much like either of them, though he acted as if he did, anxious as he was to preserve good relations at all times. One never knew, after all, now did one now did one now did one.
J. Garrett Morris wrote:
Microsoft's Component Object Model.
...still left feeling unenlightened. On the other hand, this is the *Haskell* mailing list, so...
On Wednesday 27 June 2007, Andrew Coppin wrote:
J. Garrett Morris wrote:
Microsoft's Component Object Model.
...still left feeling unenlightened.
COM documentation does seem to have that effect on people. . . Jonathan Cast http://sourceforge.net/projects/fid-core http://sourceforge.net/projects/fid-emacs
From my point of view it is a real shame that we don't have a reliable one yet! What is with all that mumble of reusable code, interoperability and enhanced stabilty if you can't use/proof it because it is a nightmare to use it in a common project. Where common project means: windows and office integration. And that is the case at least for me. (And I doubt that I am alone with that definition of "common project".)
Andreas ----- Original Message ----- From: Simon Peyton-Jones To: Lewis-Sandy, Darrell ; haskell-cafe@haskell.org Cc: Sigbjorn Finne ; Krasimir Angelov (ka2_mail@yahoo.com) Sent: Wednesday, June 27, 2007 12:04 PM Subject: RE: [Haskell-cafe] Tools for Haskell and COM The biggest Haskell/COM project I know of was Krasimir's implementation of Visual Haskell, which was a plug-in for Visual Studio. The VS interfaces are COM ones, so he had to do lots of COM stuff. He may be able to help you. Sigbjorn Finne knows a lot about HDirect, but he's really busy with his day job at Galois! There's a bit of a chicken-and-egg problem here; the COM tools are not well maintained, so that discourages use, which in turn makes it less rewarding to work on them. What I don't know is the level of suppressed demand: if there were good tools, would lots of people start using them? Simon From: haskell-cafe-bounces@haskell.org [mailto:haskell-cafe-bounces@haskell.org] On Behalf Of Lewis-Sandy, Darrell Sent: 25 June 2007 19:08 To: haskell-cafe@haskell.org Subject: [Haskell-cafe] Tools for Haskell and COM Are there any currently maintained tools for interfacing Haskell with COM objects? It appears that both Haskell script and Haskell direct haven't been updated since the turn of the century, and have fallen out of step with recent library changes. ------------------------------------------------------------------------------ _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
participants (10)
-
Andreas Marth -
Andrew Coppin -
Bayley, Alistair -
J. Garrett Morris -
Jon Cast -
Krasimir Angelov -
Lewis-Sandy, Darrell -
shelarcy -
Simon Peyton-Jones -
Tim Docker