bout this matter was
> from the other point of view: Short lines are good for diff/patch files.
>
>
> Are there more people here with ADD (or ADD-history) and long-lines-disorder?
> Or is that just me?
>
>
> - marc
>
>
>
>
>
> Original-Nachric
I also stick to a pretty rigid 78 characters. Doing so actually helps
me fit more code onto my screen at a time because I usually have two
or three columns of open files side by side. I find that I need this
more often than I need to see a single function on a page (thanks to
Haskell's traditiona
This is one of the more subtle corner cases of Heist. My default, splices
are recursively processed. So when testSplice is executed for the
tag, the results are fed back into splice processing. I think this is the
right thing to do because it makes behavior less sensitive to evaluation
order.
Interesting data point. I think my initial thoughts can be summarized with
the suggestion that this thread would be better served by a little irony
and a new subject: "Reuse Considered Harmful".
On Thu, Aug 30, 2012 at 1:26 AM, Bryan O'Sullivan wrote:
> Since the release of the GHC 7.6 RC, I've
I'm happy to announce a new package called readable:
http://hackage.haskell.org/package/readable
This package provides simple reading of data types from ByteString and
Text using MonadPlus to handle failure. It doesn't seem like there's
a standard way to do simple reading from ByteString and
On Wed, Aug 15, 2012 at 9:19 PM, Ivan Lazar Miljenovic
wrote:
> On 16 August 2012 08:55, Brandon Allbery wrote:
>> Indeed. But the ghc release that split up base broke cabalised packages
>> with no warning to users until they failed to compile. Upper bounds were
>> put in place to avoid that ki
Tillmann Rendel informatik.uni-marburg.de> writes:
>
> > Which drawbacks do you see besides increased verbosity?
>
> Well, you did change the equation "amount (Leaf x) = x" to "amount fun
> (Leaf x) = x". In a larger example, this means that you need to change
> many lines of many functions,
Jonathan Geddes gmail.com> writes:
> Cafe,
>
> I was watching a panel on languages[0] recently and Martin Odersky (the
creator of Scala) said something about Monads:
>
>
> "What's wrong with Monads is that if you go into a Monad you have to change
your whole syntax from scratch. Every single
pranjal pandit gmail.com> writes:
>
>
> Hi,I would like to work on improving the HDBC as a GSOC project 2012. I have
> a previous working experience with Django and its ORM and I had a look at
> Amnesia (http://amnesia.sourceforge.net/user_manual/manual.html) which is a
> SQL database interface
Fundamentally, Software Copy Protection (as well as DRM) is an
unsolvable problem. It's basically like saying that you want to give
someone something and not give it to them at the same time. With
physical products there are physical properties that you can use to
accomplish some aspects of this.
I haven't tested it, but I think you're looking for something like this:
searchTree2 :: (a -> Bool) -> TreeLoc a -> Maybe (TreeLoc a)
searchTree2 pred rootLoc =
if pred (getLabel rootLoc)
then Just rootLoc
else firstChild rootLoc >>= siblings
where siblings loc = searchTree2 pred loc `
Interesting. It seems to me that the only solution for the
BSD-oriented haskell community is to practically boycott GPL'd
libraries. From what I understand, this is exactly what the LGPL is
for. I've known the basic idea behind the GPL/LGPL distinction for
quite awhile, but I didn't realize that
On Sun, Feb 14, 2010 at 8:39 AM, Andrew Coppin
wrote:
> MightyByte wrote:
>>
>> I like that idea. When I was first learning Haskell, I remember
>> spending a non-trivial amount of time trying to figure out what '$'
>> did. I incorrectly assumed
I like that idea. When I was first learning Haskell, I remember
spending a non-trivial amount of time trying to figure out what '$'
did. I incorrectly assumed that it was provided by some library. '!'
and '~' would certainly be other good candidates for this kind of a
page. These types of thing
On Thu, Feb 11, 2010 at 5:28 AM, Limestraël wrote:
> Eventually, I think using cabal during development may be convenient. The
> only drawback is that you have to specify each dependency...
I actually think this is a benefit, not a drawback. In one of my
projects where I used makefiles, I was de
The latest darcs head for happstack has changed the quickcheck
dependency to > 2. You might try that.
On Tue, Feb 9, 2010 at 7:13 AM, Thomas Girod wrote:
> thanks Lars and Max. It did the trick, except for one small detail :
>
> MissingH needs the "testpack -any" dependency, but cabal does not
>
I've been seeing a steady stream of similar resource vanished messages
for as long as I've been running my happstack app. This message I get
is this:
: hClose: resource vanished (Broken pipe)
I run my app from a shell script inside a "while true" loop, so it
automatically gets restarted if it cr
Hi,
I'm also a happy linode customer. However, my happstack app eats a
lot of memory. I currently have plans to switch to prgmr.com because
their hosting plans give you much more RAM / dollar than any other
hosting company I've seen ($20 / month for a gig of RAM).
On Sun, Jan 31, 2010 at 4:37 P
The example you came across is probably using HSP [1] to generate
HTML. Happstack isn't tied to a specific method of generating HTML.
You could use HSP or other libraries such as html-minimalist [2],
xhtml [3], HStringTemplate [4], or even plain old manual construction
of strings.
[1] http://www.
It strikes me that this question may be related (perhaps distantly) to
Godel's incompleteness theorem. Anyone else see similarities here?
On Thu, Jan 7, 2010 at 7:32 AM, Johannes Waldmann
wrote:
> Dear all,
>
> It's not exactly Haskell-specific, but ...
> I am trying to track down the origin of
On Thu, Dec 10, 2009 at 11:56 AM, Sebastian Sylvan
wrote:
>
>
> On Thu, Dec 10, 2009 at 3:30 PM, John D. Earle wrote:
>>
>> My intuition says that laziness and purity are distinct whereas yours says
>> that purity is a necessary condition. This is what needs to be reconciled.
>
> I think laziness
On Thu, Dec 10, 2009 at 9:50 AM, John D. Earle wrote:
> in progress. The Haskell creed appears to be, This is the way so stick to
> it! The idea appears to be that by sticking to the program the problems will
> be overcome in time and we will be left with all the glorious goodness. At
I think thi
I can't compare it with Knuth's fascicle, but the FXT book (linked to
from http://www.jjj.de/fxt/) has a whole chapter on bit wizardry and
is another excellent resource along these lines.
On Wed, Nov 18, 2009 at 6:22 PM, Casey Hawthorne wrote:
> If you haven't bought any of Knuth's fascicles yet,
On Tue, Nov 10, 2009 at 4:29 PM, Ketil Malde wrote:
> MightyByte writes:
>
>> After a bit of googling, I came to the conclusion that I needed to
>> compile it with "ghc --make -static -optl-static Foo.hs". Using only
>> "-static" or "-optl-stati
cally linked binary. But when I compile with both those
parameters I get a bunch of linker errors:
/home/mightybyte/.cabal/lib/network-fancy-0.1.4/ghc-6.10.4/libHSnetwork-fancy-0.1.4.a(Fancy.o):
In function `s6ks_info':
(.text+0x3068): warning: Using 'getaddrinfo' in statically l
25 matches
Mail list logo
