From ndmitchell at gmail.com Thu Aug 7 17:45:16 2008 From: ndmitchell at gmail.com (Neil Mitchell) Date: Thu Aug 7 17:44:51 2008 Subject: [Yhc] Core to Bytecode? In-Reply-To: <583786.95715.qm@web25213.mail.ukl.yahoo.com> References: <583786.95715.qm@web25213.mail.ukl.yahoo.com> Message-ID: <404396ef0808071445s526578c5kda36f5b7cbf4a4d2@mail.gmail.com> Hi Holger, > currently I'm playing around with transformations of YHC core files. I would like to run the resulting programs, but the haskellwiki page says that Yhc can't compile Yhc Core files to bytecode. Is there a quick-and-dirty way to use the functions that already exist in the YHC codebase for this? I don't need fancy compiler options or something like that, I just want to test small example programs. In the Supero code there is some stuff that converts YHC Core back into Haskell which can then be run. I don't guarantee it will work though. http://www-users.cs.york.ac.uk/~ndm/supero/ There is also the HHI stuff which can run YHC Core: http://www-users.cs.york.ac.uk/~mfn/hhi/index.html Tom was working on converting the front end to use Yhc Core, but I'm not sure how far he got. Checking the source might be the easiest way. Thanks Neil From dons at galois.com Thu Aug 21 14:18:03 2008 From: dons at galois.com (Don Stewart) Date: Thu Aug 21 14:17:03 2008 Subject: [Yhc] Re: [Haskell-cafe] CouchDB module in Yhc source tree: clarification, and small problems with other packages In-Reply-To: References: Message-ID: <20080821181803.GC10969@scytale.galois.com> magnus: > Sorry for not responding earlier but I didn't pay attention to this > thread at the time. The reason for finding it now is that I listened > to the FLOSS Weekly's episode on CouchDB yesterday; I stumbled on this > email from a search for haskell+couchdb. > > On Sat, Jan 5, 2008 at 4:14 PM, Dimitry Golubovsky wrote: > > 4. The dataenc package (http://code.haskell.org/dataenc/devo/) from > > which I pulled the Codec.Binary.Base64 module. The package may need > > some adjustment to GHC 6.8.x packages structure as only "base" listed > > in build-depends does not seem to be enough: when building it, Cabal > > complains for hidden packages such as collections (which I had to add > > manually to the cabal file), etc. Is it some problem with my GHC > > setup, or does just the dataenc.cabal need to be updated? > > As the author of dataenc I'm interested in fixing any problems you see > with it. Maybe you could offer some more information: > > 1. Is this still a problem? (I'm using GHC 6.8.2 and I'm having no > such problems at the moment.) > 2. What can I do to make sure that I get contacted if similar issues > come up in the future? (Currently bugs can only be reported by > contacting me directly, preferably via email. Since you didn't I > suspect I haven't communicated that clearly enough though.) I think the best result here would be to put a CouchDB binding on hackage. Is anyone in a position to do this? -- Don From golubovsky at gmail.com Thu Aug 21 14:29:21 2008 From: golubovsky at gmail.com (Dimitry Golubovsky) Date: Thu Aug 21 14:28:12 2008 Subject: [Yhc] Re: [Haskell-cafe] CouchDB module in Yhc source tree: clarification, and small problems with other packages In-Reply-To: <20080821181803.GC10969@scytale.galois.com> References: <20080821181803.GC10969@scytale.galois.com> Message-ID: Don & All, On 8/21/08, Don Stewart wrote: > I think the best result here would be to put a CouchDB binding > on hackage. > > Is anyone in a position to do this? As for myself, honestly, I did not plan to do this at this time as I am busy with other stuff (Yhc Core conversion). I'd be glad to help anyone who is willing to put CouchDB interface on Hackage. I'd like to note though that this may be a bit premature at the moment. CouchDB has been going through significant redevelopment within Apache Incubator (I am not a developer, but just watch silently), and what is available within the Yhc source tree may not work properly with the current CouchDB: it was for 0.7.x while they have 0.8.x in the incubator. So I would wait for "graduation" of CouchDB from the incubator, or at least checked with its core developers regarding API stability. Besides, the CouchDB interface in question was written only to satisfy the needs of the Yhc Web Service and may be missing some pieces, although it may be good for a starting point. Thank you. -- Dimitry Golubovsky Anywhere on the Web