ly
the same way at runtime. In order to act exactly the same way at
runtime, if you write newtype X = X A, X _|_ has to be
indistinguishable from _|_ at runtime. In other words, the data
constructor X has to be strict. In types declared with "data",
constructors are lazy -- if they wer
estion as "why can't you have newtypes with
multiple fields?" -- i.e., newtype X = X A B C -- and that's the
question I was answering. But maybe I misunderstood.
Cheers,
Tim
--
Tim Chevalier * catamorphism.org * Often in error, never in doubt
"After
ing values from the stack, and so on), and
concluded that there was probably a good reason why the backend was
being worked on actively. The -fvia-C code wasn't much better.
However, this was with GHC 6.2, so obviously this suggests that
porting House to a newer GHC version might be worthwhile for
't yet finished development of the program
> which at some moment will make them able to further develop itself
> without our help. if you believe that human is superior to computer
> you should also believe that bacterium is superior to human
>
The only thing that computers can do that
7;s why I recommended the Dennett essay. The difference
between "I'm too bored" and "I can't" is actually an interesting
philosophical question, and people have written about it in detail
before.
Cheers,
Tim
--
Tim Chevalier * http://cs.pdx.edu/~tjc * Often in
;t that one of the reasons
this mailing list exists, after all? :-)
Cheers,
Tim
--
Tim Chevalier * http://cs.pdx.edu/~tjc * Often in error, never in doubt
"...It's wonderful that I can trust you not to spit in my milk, but
what's the point if you're going to drink from the bottle?&q
kes, and thus might not
be receptive to the siren song of referential transparency :-)
Cheers,
Tim
--
Tim Chevalier * http://cs.pdx.edu/~tjc * Often in error, never in doubt
"You never have to aspire to difficulty, darling. It arrives,
uninvi
lenty of
other interns around to keep me company even during the fall, and
Cambridge is a lovely place to spend an autumn as well.
Cheers,
Tim
--
Tim Chevalier * http://cs.pdx.edu/~tjc * Often in error, never in doubt
"The more you talk, the more I get / a sense of something that hasn't
h
On 1/26/08, Paul Johnson <[EMAIL PROTECTED]> wrote:
> * Say "computers are cheap but programmers are expensive" whenever
> explaining a correctness or productivity feature.
This is true only if talking to people in high-income nations.
Cheers,
Tim
--
Tim Chevali
On 1/26/08, Paul Johnson <[EMAIL PROTECTED]> wrote:
> Tim Chevalier wrote:
> > This is true only if talking to people in high-income nations.
> >
> Even in low-income nations, its only false in the short term. If you
> have skilled programmers with computers and Intern
etc. I don't really know enough to give a more complete answer
to your question. But my original point is that saying labor is always
expensive and hardware is always cheap by comparison is a culturally
biased statement, at least right now, on January 26, 2008.
Cheers,
Tim
--
Tim Chevalier *
r you
to sell it to a 300-person hall full of undergrads, most of whom are
likely to start checking email the moment you say something that bores
them.
Disclaimer: This entire message consists of my personal opinions and
does not represent the opinions of anybody else, and probably won't
repre
Object Box where
> > pos = return . BasicalType.pos
> > instance Object Chain where
> > pos = BasicalType.pos
>
> > -- Main.hs
> > import Type
> > ...
>
Be careful not to confuse Haskell's type class system with the idea of
a "class" in obje
"Haskell", stress on the first syllable; the first syllable is like
the word "has" and the second syllable is pronounced with a schwa
where the "e" is written.
Sometimes you will hear people stress the second syllable, but that is
not Preferred.
Cheers,
Tim
--
Tim
On 1/28/08, Jeremy Apthorp <[EMAIL PROTECTED]> wrote:
> On 29/01/2008, Tim Chevalier <[EMAIL PROTECTED]> wrote:
> > "Haskell", stress on the first syllable; the first syllable is like
> > the word "has" and the second syllable is prono
ly want to ask Haskell Curry how *he*
pronounced his name, but it's a bit late for that.
Cheers,
Tim
--
Tim Chevalier * http://cs.pdx.edu/~tjc * Often in error, never in doubt
"Work is there when love is gone" -- Greg Brown
___
Haskell-C
a bit worse than anyone who actually
grew up speaking French.
Cheers,
Tim
--
Tim Chevalier * http://cs.pdx.edu/~tjc * Often in error, never in doubt
"Now I'm trying to get back to what I know that I should be / hoping
to God that I was just a temporary absentee" -- Gerard McHugh
_
On 1/28/08, Tim Chevalier <[EMAIL PROTECTED]> wrote:
> On 1/28/08, Jeremy Shaw <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > If my sources are to be believed, the following clip contains Simon
> > Peyton Jones saying 'Haskell' several times.
>
rently than I do.
>
> I think to ease the acceptance of Haskell in the broader world we should
> spell it "Hascal" and stress the second syllable. :)
>
I think to ease the acceptance of Haskell in the broader world, we
should just change the name to Schönfinkel.
Cheers,
Tim
On 1/28/08, Anton van Straaten <[EMAIL PROTECTED]> wrote:
> Tim Chevalier wrote:
> > I suppose you would really want to ask Haskell Curry how *he*
> > pronounced his name, but it's a bit late for that.
>
> Someone could ask Alonzo Church, Jr. how his one-time dat
or "haskell faq" turns up this as one of the first ten
hits:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg01153.html
which is hardly current.
So somebody should write one.
Cheers,
Tim
--
Tim Chevalier * http://cs.pdx.edu/~tjc * Often in error, never in doubt
"What you call &#
On 1/28/08, Brandon S. Allbery KF8NH <[EMAIL PROTECTED]> wrote:
>
> On Jan 28, 2008, at 21:54 , Tim Chevalier wrote:
>
> > I thought that the .wav file that Jeremy linked to should go in the
> > Haskell FAQ, if there was one, but it doesn't seem to exist.
>
&
ully useful discussion.
>
I live to serve.
> Some more messages on this subject, and I will have really to call an
> ambulance so they can take me away, far from Internet...
>
Have them stop at my place next...
Cheers,
Tim
--
Tim Chevalier * http://cs.pdx.edu/~tjc * Often in error,
people's names the way
they say them.)
(The first convention doesn't work with my last name, though the
second one does.)
Cheers,
Tim
--
Tim Chevalier * http://cs.pdx.edu/~tjc * Often in error, never in doubt
"Living with depression is like trying to keep your balance while y
s who won the battle of Hastings in 1066, beginning their campaign
> from where I usually live and work.
> ... Not forgetting that before them there were Danish Vikings, coming from
> the place where I sit now...
Indo-European turtles all the way down.
Cheers,
Tim
--
Tim
To pre-empt the next couple of questions, the numbers 17 and 23 are
from _The Illuminatus! Trilogy_ by Robert Shea and Robert Anton
Wilson, and the number 37 is from the Jersey Trilogy of movies by
Kevin Smith.
Cheers,
Tim
--
Tim Chevalier * http://cs.pdx.edu/~tjc * Often in error, never in
and 2006 CUFP (Commercial
Users of Functional Programming) workshops. The schedules have links
to slides from talks by people using FP in industry.
Cheers,
Tim
--
Tim Chevalier * http://cs.pdx.edu/~tjc * Often in error, never in doubt
"Not only would I never want to belong to any club that wou
he other hand, if you can't
think of real examples offhand, and no one else can either, maybe it's
not that important... (Examples don't have to be very complicated to
be useful, by the way. Simpler is better.)
Cheers,
Tim
--
Tim Chevalier * http://cs.pdx.edu/~tjc * Often in er
d has a semantics based on graphs. So I don't believe
Haskell doesn't have a semantics, graph-based or not... or at least
not a formal one, and if not a formal one, I don't know what you mean
:-)
Cheers,
Tim
--
Tim Chevalier * http://cs.pdx.edu/~tjc * Often in error, never in doubt
nd "email to requestors"?
I would be entertained, but perhaps this might be more on-topic on the
darcs-users mailing list (and interested parties might be more likely
to see it there, since not everyone can keep up with haskell-cafe) :-)
Cheers,
Tim
--
Tim Chevalier * http://cs.pdx.ed
in the archive), if necessary.
It would be really useful if you decided to put time into this. Thanks
in advance!
Cheers,
Tim
--
Tim Chevalier * http://cs.pdx.edu/~tjc * Often in error, never in doubt
"You never have to aspire to difficulty, darling. It arr
On 3/18/08, Walt Potter <[EMAIL PROTECTED]> wrote:
> All,
> We're running out of space when we intersect two large sets. We've
> imported Data.Set.
> Any suggestions?
>
What optimization and other compiler flags (heap size, etc.) are you
using? Have you tried p
iling before you "try to remove the lazy stuff". There's no
point in trying to optimize code until you know what's actually taking
up space.
If you have problems with profiling, then ask on the
glasgow-haskell-users mailing list.
Cheers,
Tim
--
Tim Chevalier * http://cs.pdx.ed
potentially be
useful for my work, not so as to question whether it should be on
haskell.org (I don't care about that :-))
Cheers,
Tim
--
Tim Chevalier * http://cs.pdx.edu/~tjc * Often in error, never in doubt
"It's easy to consider women more emotional than men whe
sibly as an
example of what not to do), but you could look at my half-finished
GraphicsMagick binding:
http://hackage.haskell.org/cgi-bin/hackage-scripts/package/hsmagick
Cheers,
Tim
--
Tim Chevalier * http://cs.pdx.edu/~tjc * Often in error, never in doubt
"Good memories make me feel bad / Bad
I've only read the beginning, but I recommend _Conceptual Mathematics_
by Lawvere and Schanuel for a *very* gentle introduction (seriously,
you could probably teach category theory to ten-year-olds out of this
book.) Nothing about applications there, though.
Cheers,
Tim
--
Tim Chevalier *
101 - 136 of 136 matches
Mail list logo
