Dusan Kolar wrote:
> Dear all,
>
> reading that
>
> > according the several style guides, lines shouldn't be too long
> > (longer than 78 characters).
> >
> > http://www.cs.caltech.edu/courses/cs11/material/haskell/misc/haskell_style_guide.html
> > http://www.haskell.org/haskellwiki/Programmi
Dusan Kolar wrote:
> I would like to know, whether 78 characters bound still makes a sense...
Yes, but I wouldn't fight for a single character.
> Even if I connect to my linux box with text terminal, it is not a 80x24
> characters HW text terminal, but a window emulating this in whatever
> else O
The longer a line the more difficult it is to move the focus to the
beginning of the next line when reading.
Hmm, then I must be doing something wrong, I do not fully fill program
lines... ;-)
Or my comments are too short. I do not think, this is an issue, to catch
the next line, if the pro
Jason Dusek wrote:
> Really, the whole thing makes me wish we had blasphemy laws.
>
> If any person, in speaking or in writing, shall indicate
> a preference for column widths other than 80 or indent
> characters other than spaces (`0x20`) they shall be
> compelled to present s
P.S. We really need such a well written style guide for
haskell. Python has this nice PEP (Python Enhancement
Proposals). Should we start making our own HEP?
We have one: urchin.earth.li/~ian/style/haskell.html
Yes, it's good. We should publicise it more.
Just a tought: I would l
> I think the non-applicable to code observation is very likely true –
> we'd like to be able to write nice descriptive variable names.
> In doing this, we probably want them to be more than the 1 or
> 2 characters that Haskellers traditionally use, maybe of the order of
> 5-10.
> Given this, it
Just a tought: I would like to see a guide talking about the
code itself, not about the presentation. (...)
> (...)
It's difficult because it's not a question of science, but rather a
question of aesthetics. And as anyone in the humanities can tell you,
(...)
Maybe we could learn with them:
Maurício wrote:
> Maybe we could learn with them: what about if Haskell Weekly
> News had a section on code review, like many newspapers have
> book review sections?
>
The weekly WTF?
--
(c) this sig last receiving data processing entity. Inspect headers
for copyright history. All rights reser
Xiao-Yong Jin wrote:
> Gwern Branwen writes:
>
> > I was cabalizing a package once, and I chucked into the
> > build-depends 'ghc' and made it build. About 30 seconds later, it
> > occurred to me that this was a geometry library and what the heck
> > was it doing with the GHC API? So I go looki
Richard O'Keefe wrote:
>
> On 25 Apr 2009, at 8:59 pm, Miguel Mitrofanov wrote:
>
>> Something like
>>
>> newtype MyCoolMonad = MyCoolMonad (FirstTransformer (SecondTransformer
>> (ThirdTransformer Whatever))) deriving (Functor, Monad, FirstClass,
>> SecondClass, ThirdClass, SomeOtherClass)
[...]
Christian Maeder schrieb:
> Putting commas in the front, better indicates the continuation, but the
> extra space following the open bracket "(" looks a bit odd. (Surely one
> could also leave a space before the closing bracket, although I wouldn't
> like spaces around all brackets.)
>
> The alte
Another reason for the 80 character limit: some developers have very
poor eyesight, which can be overcome with large monitors and large
fonts. This won't work if you have to scroll the code.
Regards,
John A. De Goes
N-BRAIN, Inc.
The Evolution of Collaboration
http://www.n-brain.net|
I've found that some developers have very poor taste in shirts as well,
therefore Haskell should have a dress code
Sorry I'm not buying 80 characters as a way to address bad eyesight. ;-) I
think there's supposed to be technology in the editors to deal with that...
just as we can try to find
2009/04/22 Achim Schneider :
> Jason Dusek wrote:
>> Really, the whole thing makes me wish we had blasphemy laws.
>
> I'll definitely add it to the list of questions should I ever
> conduct a job interview. Just to test how much backing people
> have for their zeal.
I'm sure you'll find plenty
Maurício wrote:
> > We have one: urchin.earth.li/~ian/style/haskell.html
>
> Yes, it's good. We should publicise it more.
Just a tought: I would like to see a guide talking about the
code itself, not about the presentation. Maybe this is ignored
because it's difficult. It's easy to get bad code
2009/04/23 Maurício :
> Maybe we could learn with them: what about if Haskell Weekly
> News had a section on code review, like many newspapers have
> book review sections?
This seems worthwhile.
--
Jason Dusek
___
Haskell-Cafe mailing list
Haskell-Ca
On Thu, Apr 23, 2009 at 8:29 PM, Achim Schneider wrote:
> Maurício wrote:
>
>> Maybe we could learn with them: what about if Haskell Weekly
>> News had a section on code review, like many newspapers have
>> book review sections?
>>
> The weekly WTF?
I'm not sure such a thing is good... At the v
Gwern Branwen writes:
> I was cabalizing a package once, and I chucked into the build-depends
> 'ghc' and made it build. About 30 seconds later, it occurred to me
> that this was a geometry library and what the heck was it doing with
> the GHC API? So I go looking, and I find a module of utility
On Fri, Apr 24, 2009 at 9:07 AM, Achim Schneider wrote:
> Xiao-Yong Jin wrote:
>
>> Gwern Branwen writes:
>>
>> > I was cabalizing a package once, and I chucked into the
>> > build-depends 'ghc' and made it build. About 30 seconds later, it
>> > occurred to me that this was a geometry library an
19 matches
Mail list logo
