Hi,
I have some problems with the error processing in HXT.
Here is a trivial example:
e <- runX (transformDoc [] someRules src dst)
transformDoc cfg rules src dst =
configSysVars cfg >>>
readDocument [] src >>>
rules >>> -- some transformations
writeDocument [] dst >>>
getErrSt
Hi Uwe,
thanks a lot for the clarification!
Indeed, I was a bit confused since all other concepts in HXT are
straight forward and easy to grasp.
When is the release of hxt-9.1 on hackage expected?
On 12/04/2010 05:49 PM, Uwe Schmidt wrote:
Hi Tobias,
I have some problems with the er
Perhaps this might help:
I wrote a kind of logger monad that inserted messages with a context.
Behind was an algebraic data type, let's say "LoggerState".
The API provided methods to add a message like this:
addError :: String -> Logger ()
addError "Fatal error occurred"
addWarning "Some warnin
Hi Klaus,
from your code I cannot tell where exactly you're stuck. A general hint
may be to have a look at the parsec library.
On 02/25/2011 09:51 AM, Hauschild, Klaus (EXT) wrote:
Hi,
Currently I'm trying to lern Haskell by doing. After doing some
examples I plan to solve an ICFP task (see
The problem is
lexOrder s@[_] = s
where you just give back what you receive, i.e. [Char].
But you claim to give back [[Char]].
Try [s] on the right-hand side.
On 05/04/2011 02:41 PM, Barbara Shirtcliff wrote:
On May 4, 2011, at 7:21 AM, Ivan Lazar Miljenovic wrote:
On 4 May 2011 13:13, Barba
I am studying Haskell database libraries.
In particular I am looking at
haskelldb and the Takusen Database.Enumerator library.
In haskelldb, there are very good ideas aiming to represent database
objects as (typeable) Haskell objects, instead of embedding SQL in plain
strings.
This is really an
Sorry for the awful message format in the first try!
I am studying Haskell database libraries.
In particular I am looking at
haskelldb and the Takusen Database.Enumerator library.
In haskelldb, there are very good ideas aiming to represent database
objects as (typeable) Haskell objects, instead
Thanks Greg,
both references are very interesting.
If I understand correctly, the DSH approach is to convert Haskell
programs into SQL and run them inside the database. This seems a good
solution when the program objective is to change data in the database
according to some business logic or
Hi!
I am pleased to announce patterns-0.0.3.
On Hackage: http://hackage.haskell.org/package/patterns
The Patterns package implements communication patterns that are often
used in distributed, message-oriented applications. The package
implements a set of basic patterns and a device to connect
