David Menendez wrote:
Here's another one:
addTriple (s,p,o) = addArc s p o . addNode s . addNode p . addNode o
I like to think it's pretty straightforward.
I suppose you could argue that these are examples of semi-point-free
style, or something. Certainly, I wouldn't want to rewrite tsArcFwd
Henning Thielemann wrote:
Since I couldn't find one, I started one on my own:
http://www.haskell.org/hawiki/ThingsToAvoid
I consider 'length', guards and proper recursion anchors.
Very interesting. It would be nice to have reasoning for the n+k
patterns thing. Guidelines that say 'don't do this'
pablo daniel rey wrote:
hello
i'm new to haskell so i'm sorry if this is a stupid question, but i'm having
problems with some basic code.
the code :
data Maybe Dir = Just Dir | Nothing
data Dir = Left | Right | Up | Down
data Piece = Vertical | Horizontal | CodeA | CodeB
flow = [(Horizontal,
[EMAIL PROTECTED] wrote:
I've got a general new person type question.
I understand that I can hide a function in a module that I am importing
if it conflicts with another identical function name.
But if the situation arises that I would like to use two identically
named functions from two
Simon Peyton-Jones wrote:
| I also have a very small start on a haskell for hackers (hackers
in
| the non-evil sense) sort of document. One this doesn't ignore I/O as
| hard or unimportant. I/O in Haskell doesn't suck. It's just that
a
| lot of people in the community don't have it as a high
Ben Rudiak-Gould wrote:
Keean Schupke wrote:
At the risk of getting off topic... the reason 'C' has printf is because
it is not polymorphic. Printf is a hack to allow different types to be
printed out, such that they did not need printInt, printFloat etc.
Many language have printf-like
Isn't Happy [1] a bottom-up parser generator in the style of yacc?
[1] http://www.haskell.org/happy/
As for parsing yacc's input files, if you can come up with an EBNF
grammar for it that avoids some of the nasty recursion possibilities [2]
then I can't see why you couldn't parse it with
Gour wrote:
Daan Leijen ([EMAIL PROTECTED]) wrote:
Hi Daan!
This new release fixes many bugs, adds basic support for MDI
applications and compiles with the latest CVS snapshots of wxWidgets.
For now, only an installer for windows is provided.
Thank you very much for your cosntant work on
Gour wrote:
Matthew Walton ([EMAIL PROTECTED]) wrote:
Plenty of ebuilds seem to work from multiple source packages... I can't
see a particular difficulty in writing one that installs wxHaskell
source and documentation simultaneously.
Thank you for pointing this out. I never came across one
George Russell wrote:
Simon Marlow wrote:
As for the width of the tab character: tab stops are every 8 columns.
Period. The Haskell report says so
Yes, true. I think it was Leslie Lamport who wrote in TeXHaX that anyone
defining an input format which includes tabs should be sentenced to ten
Simon Marlow wrote:
I think there is some software to translate some DocBook
derivate to man
pages. Maybe one could use the DocBook export mechanism of
Haddock for man
page production. Just and idea.
Haddock's DocBook output support needs a lot of work - I originally
started on the
11 matches
Mail list logo
