I've been going over my code trying to get it all to compile with
ghc -Wall -Werror
I recently ran across what may be a good reason not to use -Wall in
combination with -Werror (and similar combinations in other
compilers), at least not as the standard build switches for software
you intend to
This is an announcement of something so tiny (about 100 lines of code
including comments), I'd feel bad posting it to the haskell list, so
it'll go on haskell-cafe. This was pretty much just a project for me
to learn cabal and hackage, but it may very well actually come in
useful some day.
On Sunday 17 June 2007 08:26:45 Michael T. Richter wrote:
I'm trying to build Yi (from the darcs repository) to take a look at it.
The README that comes with it says it's a standard Cabal project so do
what you normally do (paraphrased slightly).
GNU autotools comes with a standard boilerplate
Well, since we're on the subject and it's only the Cafe list, what is
it that you find messy about Linux that you would want to be solved by
some hypothetical Haskell OS?
The hypothetical Haskell OS, especially if it were targeted toward 64
bit machines, could keep processes from messing
Normally I've seen capabilities used so that you can't access
anything you can't name. Can you elaborate a little?
He's saying that the language itself prevents programs from writing
outside their address spaces
Yep. Capabilities are usually not actually unforgeable, they are just
picked
Every capability system I've seen works like Unix file descriptors. The
kernel assigns capability numbers, and since the numbers are only valid
in one process, and the only valid capability numbers are to
capabilities your have, there is no danger caused by guessing.
You know, when I typed
