On Sun, May 27, 2007 at 10:49:41PM +0100, Ian Lynagh wrote:
> On Sun, May 27, 2007 at 02:16:15PM -0700, John Meacham wrote:
> > On Sun, May 27, 2007 at 08:28:25PM -, GHC wrote:
> > >
> > > Exporting a module that isn't imported doesn't fail.
> &
odule List ) where
> }}}
Actually, I don't think this is a bug, 'module Foo' in the export list
is defined to export all names in scope which are of both in scope under
the names 'Foo.bar' and 'bar' and both names refer to the same entity.
There is no pa
ly the larger the program you are compiling is, so perhaps it has
something to do with the rather large lag between the time ghc parses
the files and actually uses the results of the parse to compile the .o
file. which can easily be tens of minutes for a large project. This is
just supposition though.
implicitly
module Main(main) where
which is very nice for optimizing compilers.
John
--
John Meacham - ⑆repetae.net⑆john⑈
___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
n of ghc works just fine on x86_64 if you modify it to
just pass '-m32' to all the tools. it would be nice if the driver script
checked uname -a and passed -m32 or -m64 as appropriate, so you can
trivially compile both 32 bit and 64 binaries on the same system. by
running '
On Mon, Mar 26, 2007 at 09:51:02PM -0700, Stefan O'Rear wrote:
> On Mon, Mar 26, 2007 at 09:31:41PM -0700, John Meacham wrote:
> > On Mon, Mar 26, 2007 at 09:23:13PM -0700, Stefan O'Rear wrote:
> > > On Mon, Mar 26, 2007 at 09:15:35PM -0700, John Meacham wrote:
> &
On Mon, Mar 26, 2007 at 09:23:13PM -0700, Stefan O'Rear wrote:
> On Mon, Mar 26, 2007 at 09:15:35PM -0700, John Meacham wrote:
> > actually, this is not true for the specific case of testing against zero
> > on x86 at least. there is a 'zero flag' that is set
an operation is zero. whereas for compares, you actually need to load
zero into a register and cmp against it.
though, there could be other things going on with ghc of course.
John
--
John Meacham - ⑆repetae.net⑆john⑈
___
Glasgow-haskell-bugs ma
jhc calls it unsafeCoerce__ and it lives in Jhc.Prim. In general, I use
the trailing __ to mean what abafthash does in ghc.
John
--
John Meacham - ⑆repetae.net⑆john⑈
___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http
The other reason is
principle of least surprise. stderr is pretty much always unbuffered by
default (as in, ANSI c specifies it, and most (all?) languages with a
concept of buffering follow suit) . I would find it quite odd for
haskell to be different than unix norms.
for multithreaded logging, I h
om then the next write or read call is
guarenteed to not block, no matter what its size. (you just may get a
short read or write)
John
--
John Meacham - ⑆repetae.net⑆john⑈
___
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
Why do we set file descriptors to nonblocking mode anyway if they are
waited on by a select. there shouldn't be a need to use both mechanisms.
John
--
John Meacham - ⑆repetae.net⑆john⑈
___
Glasgow-haskell-bugs mailing list
Glasgow-haskell
or http://sourceforge.net/projects/ghc/.
it only happens when i try to compile with profiling enabled.
--
-------
John Meacham - California Institute of Technology,
hc/.
make: *** [mfl.o] Error 1
--
------
John Meacham http://www.ugcs.caltech.edu/~john/
California Institute of Technology, Alum. [EMAIL PROTECTED]
--
import Char
import Maybe(fromJust)
data Code = Co
14 matches
Mail list logo
