Experimental IRC log happs-2007-11-17

Available formats: content-negotiated html turtle (see SIOC for the vocabulary)

Back to channel and daily index: content-negotiated html turtle

These logs are provided as an experiment in indexing discussions using IRCHub.py, Irc2RDF.hs, and SIOC.

04:49:18<cedricshock>When I run ../sp runhaskell -ihaskell haskell/Main.hs in HAppS-Begin I get: haskell/State.hs:23:37:
04:49:18<cedricshock> Not in scope: type constructor or class `Private'
04:50:08<sclv>cedricshock: it looks like the repo is broken for the moment -- i guess shapr & co. plan to have it fixed within the day.
04:50:25<cedricshock>sclv: Thanks.
04:52:55<cedricshock>By the way, where did the good examples of using IxSet go?
06:59:42<cedricshock>Is there a way to get the repos before they broke?
07:40:09<mmmdonuts>cedricshock, there's a 0.9.1 tag in the repos which you can specify with "darcs get --tag=0.9.1", but that's fairly old. You might want to pull a bunch of patches after that using "darcs pull".
07:41:44<mmmdonuts>The repos supposedly broke around Tuesday, so don't pull patches too close to that date.
07:42:51<mmmdonuts>One thing about doing that is I think building with Searchpath will use the latest repos by default. You might need to do a cabal build using your local copy of the repos.
07:43:49<mmmdonuts>Hope any happs experts will point out if there's an easier way to do this.
16:53:25<lars_o>hello
16:55:32<lars_o>I've got a newbie question here, is it possible to use a database when handling requests in happs, given that MACID is not in the IO monad put database packages such as HDBC are in IO?
16:56:42<lars_o>O do understand that it is part of the idea in HAppS not to have a database, but I'd need to speak to one for integrating with some other applications which use the existing database
16:59:08<lars_o>s/^O/I
17:16:32<Saizan_>lars_o: well, the new api is directly in IO so there's no problem (but currently the repos won't build), with 0.8.8 it's easy to do IO if it doesn't modify the state
17:20:18<lars_o>so with the old API if I want to have some interaction of app state and what's in the database i'd need to sort of distribute it on two requests
17:21:23<lars_o>For instance, I will need the database for authenticating users
17:22:09<lars_o>and whether a user is authenticated or not would obviously mean a modification of the state

Back to channel and daily index: content-negotiated html turtle