Hello glasgow-haskell-users,
in the following definitions:
> {-# INLINE getInteger #-}
> getInteger = ... -- large definition that will be not inlined
> -- without pragma
>
> instance Binary Integer where
> get = getInteger
is Integer.get will be inlined or not?
--
Best rega
On Tuesday 07 November 2006 16:30, Simon Peyton-Jones wrote:
> The bit that does the dependency analysis is called the Occurrence
> Analyser. Its in compiler/simplCore/OccAnal. A single run of the
> occurrence analyser will produce a fully-dependency-analysed program. Maybe
> that's what you want
Hi
Anyway, you say you are working on a command line interface - OK, but
I think the current situation is just a bit embarrassing, and I have
something that works now. I can access all Perl documentation with
'man', and that is very convenient. It is just two words, e.g.:
Fair enough, you are
> Yes, I know command line completion works - but only for files, not
> for anything else, and there is no way to make it work for other
> things. However, I know that zsh can do funky things like
> autocompleting ssh paths etc - and I think I remember seeing that
> there was some way a program cou
| This is great! However, I don't understand why:
| 'incL_afU',
| '$dNum_alp',
| 'fromInteger_alm',
| 'lit_al2' and
| '+_al3' are all listed under the same letrec?
The desugarer simply does whatever is easiest, leaving it to the simplifier to
untangle the resulting dependencies. Doubtless we cou
> Hi
>
>> How would it work on Unix? I assume that the command-line program just
>> takes it's input "from the command line", so it doesn't get invoked
>> until after you've finished typing the command...
Not necessarily true if completion is involved ... see below.
> However, I know that zsh can
Hello,
I had this example that was working with earliest versions of GHC but
it doesn't work with GHC-6.6.
$(deriveReflectable ''[])
Above this isn't a double quote but two single quotes. It may not be
clear with some fonts. Is this a bug or just there is a change in the
syntax? The error that
Hi
How would it work on Unix? I assume that the command-line program just
takes it's input "from the command line", so it doesn't get invoked
until after you've finished typing the command...
Unless this is a proposal to create a console version of hoogle, a bit
like ghci, which could take adva
Simon Marlow <[EMAIL PROTECTED]> wrote:
> > When I use `seq`, it is sometimes in a construction like
> >
> > unsafePerformIO (emit "squawk!) `seq` x
>
> My take on this kind of thing is that if you want a specific
> operational behaviour, then you're doing something
> implementation-specifi
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Neil Mitchell
>
> > - command-line autocompletion
>
> No, how do I add it? I use Windows which doesn't support this, but if
> someone gives me the technical details of how to do it, I'm sure I can
> add it.
How would it work
> Since you already have a Makefile, why not add this to it:
>
> SRCS = Source.hs ...
> prog: $(SRCS)
> ghc --make $(SRCS) -o prog
>
> and then just say 'make' to build your program? Surely that's easier than
> typing 'ghc
> --make-command=make ...'? Maybe I'm missing something?
Hi Sim
Hi
- ability to index any library
Yes, runhaskell Setup haddock -hoogle will generate a hoogle database
for any library. Hoogle 4 (currently in development) will make
searching multiple libraries much much easier.
- ability to use from the console
Yes, although may currently be a bit broke
Simon Marlow schrieb:
>>ghcpkg01(normal)
>>ghcpkg03(normal)
>
> Any idea why these are failing for you?
Maybe rather than using my installed ghc-pkg (that lists haskell-src)
some inplace ghc-pkg was used:
ghc-pkg: dependency haskell-src doesn't exist (use --force to override)
make[2]: **
Hi Neil,
I've seen hoogle and I like it. Does Hoogle have the following
features?
- ability to index any library
- ability to use from the console
- command-line autocompletion
Of course, there are many features that Hoogle has, which my program
is missing.
Frederik
On Tue, Nov 07, 2006 at 12:
The {-# ORIGIN ... #-} keyword sounds like a nice solution, but
wouldn't it require creating each generated file initially by hand, so
that the compilers know that it exists? I'd rather have a build system
where I can delete all of the generated files before distributing my
code, and still have com
John Meacham wrote:
I would definitely like something like this.
like
{-# PREPROCESS drift-ghc #-}
to specify the file should be preprocced by drift-ghc.
I worry that putting details of the build procedure into the source file will
lead to problems. Often build parameters need to be config
Frederik Eaton wrote:
Hello,
I have a proposal for ghc. I think that it should take a new option,
say "--make-command". This will specify a command to be run whenever a
source file is read in by ghc. The command will be passed an argument,
which is the name of the source file. The idea is that t
Christian Maeder wrote:
Did someone run the test-suite of the binary distributions?
http://www.haskell.org/ghc/dist/6.6/ghc-6.6-ppc-apple-darwin.tar.gz
http://www.haskell.org/ghc/dist/6.6/ghc-6.6-i386-apple-darwin.tar.bz2
I've build a (ppc-) mac-distribution from sources and my results are
show
Malcolm Wallace wrote:
Ross Paterson <[EMAIL PROTECTED]> wrote:
When I've used seq, it's to ensure that a function is strict in that
argument, and therefore has been evaluated before the function is
called. (If the language had unlifted types, I might have used those
instead). Beyond that, I d
On Mon, Nov 06, 2006 at 12:53:55PM +, Simon Marlow wrote:
> Incedentally, this is also one reason I think lazy I/O is a wart (despite
> its obvious usefulness): because it necessarily requires talking about
> evaluation order.
What is lazy output? Buffering?
___
On Mon, Nov 06, 2006 at 05:21:04PM +, Ross Paterson wrote:
> Apart from that, the only thing wrong with seq is its name.
I take back that part. Simon's "strong hint" suggestion looks like a
good idea. It's just one of a number of implicit assumptions we make
about operational behaviour. Aft
Seth Kurtzberg <[EMAIL PROTECTED]> writes:
> > how about searching code that's outside of the standard library? Hoogle
> > doesn't seem to know about HaXml, or haskelldb for example (maybe I am
> > missing something obvious)
>
> You want to distinguish between capabilities, and the fact that the
22 matches
Mail list logo
