- Forwarded message from Richard Braakman [EMAIL PROTECTED] -
Date: Tue, 03 Dec 2002 03:26:54 +0200
From: Richard Braakman [EMAIL PROTECTED]
Subject: Bug#171518: ghc --make does not play nice with FFI wrapper
To: Debian Bug Tracking System [EMAIL PROTECTED]
Reply-To: Richard Braakman
Package: ghc5
Version: 5.04-1
Severity: normal
I have a module SDL.Bare.Audio with this declaration:
foreign import ccall safe wrapper
mkSDL_AudioSpec_Callback :: SDL_AudioSpec_Callback u -
IO (FunPtr (SDL_AudioSpec_Callback u))
When compiling
Hi there,
it includes quite a bit more 'stuff' -- profiling libraries + a bunch of
tools that's needed by the backend on that platform.
To help you out a little bit, I've tar'ed up the profiling libraries
separate
from the main distribution tar bundle, which shaves off some 10M.
Available via
[EMAIL PROTECTED] (Ketil Z. Malde) writes:
Malcolm Wallace [EMAIL PROTECTED] writes:
Ingo Wechsung [EMAIL PROTECTED] writes:
I wonder if the compiler could check, if all possible combinations have
been checked in a pattern match.
In ghc, use the compile-time option
Hi,
when installing ghc and hugs under SuSE linux 8.1 I got
configure: error: can not guess host type; you must specify one
It worked after I added --host=i386-linux
Christian
___
Haskell mailing list
[EMAIL PROTECTED]
On Friday, 2002-11-29, 14:12, CET, Ashley Yakeley wrote:
At 2002-06-29 14:43, Wolfgang Jeltsch wrote:
To simplify things a bit, let's take a simpler Parser type which doesn't
use monad state transformers but simple state transformers instead. This
makes the type ParserState simpler. You
At 2002-12-06 15:57, Wolfgang Jeltsch wrote:
I cannot see how this relatively simple representation can be used to
describe
certain parsers. If I would use Identity for baseMonad, I would have a type
for simple parsers. MyParser Identity would essentially be token - output.
You can't use
John Meacham [EMAIL PROTECTED] writes:
rather than start layout blocks right after the 'let' 'do' or 'where',
put them on the next line with one more tabstop than the current
line.
I've also a bit baffled by all the people apparently struggling with
layout; I realize the rules are a bit
Wether spaces or tabs are better in source files is a matter of taste and
a language should not force me to use one or another.
Well note that it doesn't only confuse compilers: if you post code for
other people to read (whose display software has their personal own
interpretation of what a
Andrew wrote:
My remark was merely in response to the claim that Haskell cares
whether you put tabs or spaces in your files. It does not, so long
as the tabs are of length 8. If your editor produces tabs of a
different size, that's a problem with your editor or the way you
dislike Haskell's
When I got somebody else's C-Code, I used gnu indent to bring
it into a layout I liked (and could easily grasp).
One of the points I like about Haskell is just its use of
space: it makes things clearer and doesn't clutter up your screen
as it does in C. I definitely had less problems with layout
Hi there,
I wonder if the compiler could check, if all possible combinations have been
checked in a pattern match.
For example:
data Colour = Red | Yellow | Green | Blue;
trafficlight Red = True;
trafficlight Yellow = True;
trafficlight Green = True;
trafficlight Blue = False;
This is
Ingo Wechsung [EMAIL PROTECTED] writes:
I wonder if the compiler could check, if all possible combinations have
been checked in a pattern match.
In ghc, use the compile-time option -fwarn-incomplete-patterns
Regards,
Malcolm
___
Haskell-Cafe
Malcolm Wallace [EMAIL PROTECTED] writes:
Ingo Wechsung [EMAIL PROTECTED] writes:
I wonder if the compiler could check, if all possible combinations have
been checked in a pattern match.
In ghc, use the compile-time option -fwarn-incomplete-patterns
Is there a warning to warn if a block is
Ingo Wechsung [EMAIL PROTECTED] writes:
Simon wrote:
There's no reason not to use 8 column tab stops, so please don't do it.
Ok, if it just looks better to me is no reason,
Tabs and spaces aren't visually distinguishable, so I'm not sure why
you conclude that looks don't matter.
As has
Fri, 6 Dec 2002 12:09:46 +0100, Ingo Wechsung [EMAIL PROTECTED] pisze:
No. My editor produces the ASCII code for horizontal tab, when I
hit the tab key. Just as it produces the ASCII code for a when I
hit the a key.
That's how it should be.
It shouln't, becase tabs are 8 spaces, which is
Ingo == Ingo Wechsung [EMAIL PROTECTED] writes:
Ingo Or, to turn it another way: What you see is not necessarily
Ingo what you get. This may be fine for ad hoc scripts that one
Ingo examines in hugs.
So is that the language's fault (because of what you get) or the
editor's fault
Kevin,
thanks for your helpfull comments.
Ingo Or, to turn it another way: What you see is not necessarily
Ingo what you get. This may be fine for ad hoc scripts that one
Ingo examines in hugs.
So is that the language's fault (because of what you get) or the
editor's fault (because
From: Ingo Wechsung [EMAIL PROTECTED]
...
Currently, I expand tabs to 4 spaces only, so
\tx=bar
looks like
foo = bar
to me when the compiler sees
foo = bar
If you want to go the layout way perhaps someone/you could put in a compiler
option for tab expansion. Check in
Peter wrote:
Currently, I expand tabs to 4 spaces only, so
\tx=bar
looks like
foo = bar
to me when the compiler sees
foo = bar
If you want to go the layout way perhaps someone/you could put in a compiler
option for tab expansion. Check in
On Thu, 5 Dec 2002 21:49:27 +0100
Ingo Wechsung [EMAIL PROTECTED] wrote:
So I will write the braces and semicolons. It's better anyway in my
opinion.
I am not going to change my editing habits just to make hugs or ghc
happy.
What about using untabified files? Or an haskell-aware
21 matches
Mail list logo
