I was planning on making the caller deal with keeping track of cookies
between requests. My cookie idea only solves the problem of cookies
persisting through a redirect chain - not between subsequent request chains.
Do you think that Network.HTTP.Conduit should have a persistent cookie jar
between
On Wed, Jan 25, 2012 at 8:18 PM, Myles C. Maxfield
wrote:
> Alright, that's fine. I just wanted to be explicit about the interface we'd
> be providing. Taking the Request construction code out of 'http' and putting
> it into its own function should be a quick change - I'll have it to you
> soon. O
That is one of the wonderful things about haskell, most languages have
a negative correlation between codesize and productivity, however with
haskell there is a strong positive correlation. You can re-use so much
that as your code base grows it becomes easier to add new features
rather than harder.
Hi Joey,
Apologies for such a late reply. I don't know if others have replied on
-cafe; it has become too high-volume for me to follow of late. There
are several options. MissingH is one. I have accepted patches there
for a long time. Another is that now that Hackage/Cabal foster easy
in
Lesson = don't open e-mail client while borderline asleep.
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
On 25/01/2012 16:13, R J wrote:
hello Haskell the holidays are coming up soon and I think this can help
http://www.news13open.com
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
_
On Wed, Jan 25, 2012 at 7:38 PM, Yves Parès wrote:
> But I haven't found a way to tell GHCI to fully evaluate 'x' but _not_ print
> its value.
Use the :force, Yves!
> let {a = htrace "a" 12; b = htrace "b" 29; c = htrace "c" 10; d = htrace "d"
> 90; x = htrace "," (htrace "+" (a+b), htrace "*"
Hi, nice little package!
I just made a fork and added a new function makeHTrace to be able to have
separate variables 'level'.
I also add the htrace type signature (or else haddock won't generate
documentation for this module):
https://github.com/YwenP/htrace
I was also investigating in a way to
On 12-01-25 04:06 PM, Yves Parès wrote:
1) Is there some documentation about it?
GHC comes with a user guide in HTML somewhere on your disk.
It is also on the GHC website, but I much prefer everyone to know and
find it on his/her disk first.
People spend lifetimes browsing the web, and not
On Wed, 25 Jan 2012 22:06:34 +0100, Yves Parès
wrote:
Hello,
By randomly typing : under GHCI, I discovered it could be used as a
debugger (:breakpoint, :step, etc.)
Three questions in that regard:
1) Is there some documentation about it?
http://www.haskell.org/ghc/docs/latest/html/users_gu
hello Haskell the holidays are coming up soon and I think this can help
http://www.news13open.com
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
Hello,
By randomly typing : under GHCI, I discovered it could be used as a
debugger (:breakpoint, :step, etc.)
Three questions in that regard:
1) Is there some documentation about it?
2) I haven't investigated much, is that fairly thorough and convenient?
Does some people over here use those funct
Hello, café.
Recently I asked about tcp server libraries [1] and there was only one
answer haskell-scallable-server [2], but in that package there was some
dependencies and server logic that are not good for my task.
So I decided to make a library with skeletons for different types of
tcp server
I assume by static semantics you mean the renamed Haskell source code.
Due to template Haskell it (currently) is not possible to run the
renamer and type checker separately. Note that the type checker
output is very different in shape from the renamed output. The
renamed output mostly follows the
Alright, that's fine. I just wanted to be explicit about the interface we'd
be providing. Taking the Request construction code out of 'http' and
putting it into its own function should be a quick change - I'll have it to
you soon. One possible wrench - The existing code copies some fields (like
the
The nice thing is that this way, nobody can force me to handle cookies. ;-)
Might be that usage patterns emerge, which we can then codify into
functions later.
Am 25.01.2012 08:09 schrieb "Michael Snoyman" :
> On Wed, Jan 25, 2012 at 9:01 AM, Myles C. Maxfield
> wrote:
> > Sorry, I think I'm st
Look how one can watch the evaluation tree of a computation, to debug
laziness-related problems.
You might like the old Hood/GHood:
http://hackage.haskell.org/package/hood
http://hackage.haskell.org/package/GHood
Background info/papers:
http://www.ittc.ku.edu/csdl/fpg/Tools/Hood
http://www.it
Thanks!
I released it:
http://hackage.haskell.org/package/htrace
http://github.com/jkff/htrace
On Wed, Jan 25, 2012 at 4:18 AM, Felipe Almeida Lessa <
felipe.le...@gmail.com> wrote:
> Really nice! Looks like it could be a useful mini-package on Hackage.
>
> --
> Felipe.
>
--
Eugene Kirpich
18 matches
Mail list logo
