> > like what? seriously, what features would you _use_?
> Didn't try yet, therefore I'm asking :-)
always the same effect:) yes, there are features one would like
to see in a language-aware development environment, and that
aren't well supported for Haskell in current editors/IDEs. but
the main r
Andreas Rossberg wrote:
> > > The most flexible but safe solution is to simply define the indentation
> > > as the sequence of indentation characters used. Two consecutive lines
> > > are indented consistently whenever one indentation is a prefix of the
> > > other. Hence you may freely mix diffe
Claus Reinke ([EMAIL PROTECTED]) wrote:
> > I've 'discovered' that latest KDevelop (3.0) has some sort of support for
> > Haskell development.
>
> like what? seriously, what features would you _use_?
Didn't try yet, therefore I'm asking :-)
But I saw that haskell is in the the table of support
> I've 'discovered' that latest KDevelop (3.0) has some sort of support for
> Haskell development.
like what? seriously, what features would you _use_?
> Although pretty new to Haskell, I'm looking for adequate IDE and would like
> to hear if someone can share his/her experiences in using KDeve
Hi!
I can't find any function in the Fudgets-library to do this:
(F a b) -> (F a (a, b))
That is, I have a fudget taking input of type a and giving output of
type b, and I want to convert it to a fudget taking input of type a
and giving output of type (a, b). All I want to do is to resend the
i
I think I've managed to create a version of POpen to go with Hugs under
Windows. (It all compiles/links, but I haven't yet got a stand-alone test
case for it).
So now I'm pushing ahead with trying to get the HXML toolbox running under
Hugs/Windows, and I've hit a snag with the Regex library.
> This just shows how deeply ingrained the ascii plain text mindset is
> in the programming community. I don't expect anything like this to ever
> fly, for this reason. You guys won't let it. :(
(Sorry, but how did ascii get in there? Was the argument for
Unicode or HTML?)
As for mindset, the
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
George Russell wrote:
> The most flexible but safe solution is to simply define the indentation
> as the sequence of indentation characters used. Two consecutive lines
> are indented consistently whenever one indentation is a prefix of the
> other. Hence you may freely mix different indentation ch
Andreas wrote:
> The most flexible but safe solution is to simply define the indentation
> as the sequence of indentation characters used. Two consecutive lines
> are indented consistently whenever one indentation is a prefix of the
> other. Hence you may freely mix different indentation characters
> Wolfgang Thaller writes (to the Haskell mailing list):
>
> > IMHO, there should only be warnings about tabs when their
> > size makes a difference to the meaning of the program,
>
> I agree and would suggest an even more stringent test to
> warn against
>
> > a = let x = 1
> > y = 2
Am Sonntag, 25. Januar 2004 23:42 schrieb Sebastian Sylvan:
> Sean L. Palmer wrote:
> > Besides, the idea would be not to use , but rather some "indent
> > paragraph" tag.
>
> This is kind-of a cool idea. If I ever take a course involving writing
> my own language I'll be sure to incorporate this
Bayley, Alistair wrote:
> {-# OPTIONS -tabsize 4 #-}
>
> I think it's still a bit of a hack, but at least the author tells you what
> their tabsize was when they wrote it, so you can recover their layout. You
> could always pre-process the source yourself with sed, if the compiler
> doesn't unde
George Russell wrote:
Graham Klyne wrote (according to Wolfgang Thaller, snipped):
> I think that compilers should issue a warning when indentation that
> determines the scope of a construct is found to contain tab characters.
In an ideal world, TAB characters would never have been put into ASCII
Wolfgang Thaller writes (to the Haskell mailing list):
IMHO, there should only be warnings about tabs when their
size makes a difference to the meaning of the program,
I agree and would suggest an even more stringent test to
warn against
a = let x = 1
y = 2 -- OK
in ...
because the (vi
Graham Klyne wrote (according to Wolfgang Thaller, snipped):
> I think that compilers should issue a warning when indentation that
> determines the scope of a construct is found to contain tab characters.
In an ideal world, TAB characters would never have been put into ASCII, and
this would be my p
{-# OPTIONS -tabsize 4 #-}
I think it's still a bit of a hack, but at least the author tells you what
their tabsize was when they wrote it, so you can recover their layout. You
could always pre-process the source yourself with sed, if the compiler
doesn't understand the option.
> -Original M
Hi!
I've 'discovered' that latest KDevelop (3.0) has some sort of support for
Haskell development.
Although pretty new to Haskell, I'm looking for adequate IDE and would like
to hear if someone can share his/her experiences in using KDevelop (or some
other) IDE for Haskell development?
(otherwi
18 matches
Mail list logo
