[ ghc-Bugs-646201 ] ghc-5.04: panic! ... tySplitTyConApp ...

2002-12-02 Thread noreply
Bugs item #646201, was opened at 2002-11-30 21:11 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=108032aid=646201group_id=8032 Category: Compiler Group: 5.04.1 Status: Closed Resolution: Fixed Priority: 5 Submitted By: Markus Lauer (mlauer) Assigned to:

RE: Native Threads in the RTS

2002-12-02 Thread Simon Peyton-Jones
| 2. Calling from foreign code into Haskell to a bound foreign import will | require some special handling to ensure that a subsequent call out to | foreign code will use the same native thread. Why couldn't this special | handling select the same Haskell thread instead of creating a new one?

:info in ghci

2002-12-02 Thread Hal Daume III
Any chance :info could also report fixity information, especially for symbolic identifiers? -- Hal Daume III Computer science is no more about computers| [EMAIL PROTECTED] than astronomy is about telescopes. -Dijkstra | www.isi.edu/~hdaume ___

RE: :info in ghci

2002-12-02 Thread Simon Peyton-Jones
It already does... but a bug meant it wasn't always reporting it. Now fixed in the head. SImon | -Original Message- | From: Hal Daume III [mailto:[EMAIL PROTECTED]] | Sent: 02 December 2002 16:50 | To: GHC Users Mailing List | Subject: :info in ghci | | Any chance :info could also

MacOS X (10.2.2) standalone ghc app

2002-12-02 Thread Reto Kramer
I'm trying to deliver a self contained app that I developed with ghc 5.04.1 on Mac OS X (10.2.2). It all works well if ghc is installed on the machine, but on a user-machine w/o ghc, the following file is needed: HaskellSupport.framework/Versions/A/HaskellSupport The error message is: idc_Darwin

Re: Native Threads in the RTS

2002-12-02 Thread Wolfgang Thaller
I've postponed writing up a new proposal again... But I'm going to sum up some requirements that I would like to see fulfilled - to make it clearer to others why I'm proposing such strange things... *) It should be possible for Haskell code to arrange that a sequence of calls to a given

Re: MacOS X (10.2.2) standalone ghc app

2002-12-02 Thread Wolfgang Thaller
I'm trying to deliver a self contained app that I developed with ghc 5.04.1 on Mac OS X (10.2.2). It all works well if ghc is installed on the machine, but on a user-machine w/o ghc, the following file is needed: HaskellSupport.framework/Versions/A/HaskellSupport Could someone explain why

'accept' does not seem to be thread friendly ..

2002-12-02 Thread Ahn Ki-yung
John Meacham wrote: that is what Concurrent is for, Haskell threads, (well GHC threads) are lightweight and can be used for selectlike purposes without too much overhead. I use them quite effectivly for complex networked applications.. see

Re: MacOS X (10.2.2) standalone ghc app

2002-12-02 Thread Andre Pang
On Mon, Dec 02, 2002 at 11:47:41PM +0100, Wolfgang Thaller wrote: I'm trying to deliver a self contained app that I developed with ghc 5.04.1 on Mac OS X (10.2.2). It all works well if ghc is installed on the machine, but on a user-machine w/o ghc, the following file is needed:

Re: AW: slide: useful function?

2002-12-02 Thread William Lee Irwin III
On Mon, Dec 02, 2002 at 10:37:09AM +1100, Andrew J Bromage wrote: In the interest of fairness, the declarative programming community occasionally appears to have an aversion to actual engineering. If you mention a term like design patterns, people look down their virtual noses at you like

Re: AW: slide: useful function?

2002-12-02 Thread John Hughes
On Mon, 2 Dec 2002, Andrew J Bromage wrote: ... If you mention a term like design patterns, well I love design patterns, it's just that in Haskell-land they are called higher-order functions, or polymorphic functions, etc. -- Johannes Waldmann

Re: AW: slide: useful function?

2002-12-02 Thread Frank Atanassow
John Hughes wrote (on 02-12-02 10:27 +0100): On Mon, 2 Dec 2002, Andrew J Bromage wrote: ... If you mention a term like design patterns, well I love design patterns, it's just that in Haskell-land they are called higher-order functions, or polymorphic functions, etc. -- Johannes

RE: AW: slide: useful function?

2002-12-02 Thread David Bergman
John Hughes wrote: On Mon, 2 Dec 2002, Andrew J Bromage wrote: ... If you mention a term like design patterns, well I love design patterns, it's just that in Haskell-land they are called higher-order functions, or polymorphic functions, etc. -- Johannes Waldmann

Re: AW: slide: useful function?

2002-12-02 Thread Nick Name
On Mon, 2 Dec 2002 13:05:27 -0500 David Bergman [EMAIL PROTECTED] wrote: or using highly formal language, with terms such as catamorphisms. Ok I can't resist longer. It's ages I have been wondering what's a catamorphism, and an anamorphism, and what the hell does it mean data is expressed by

Re: AW: slide: useful function?

2002-12-02 Thread Tom Pledger
Nick Name writes: : | Ok I can't resist longer. It's ages I have been wondering what's a | catamorphism, and an anamorphism, and what the hell does it mean | data is expressed by destructors and not by constructors, but I | have had no time till now. Please some of you all catamorphism |

Re: AW: slide: useful function?

2002-12-02 Thread Christopher Milton
--- Tom Pledger [EMAIL PROTECTED] wrote: Nick Name writes: : | Ok I can't resist longer. It's ages I have been wondering what's a | catamorphism, and an anamorphism, and what the hell does it mean | data is expressed by destructors and not by constructors, but I | have had no time till

Re: AW: slide: useful function?

2002-12-02 Thread Nick Name
As a reader but not an expert, I recommend http://www.cse.ogi.edu/~mpj/pubs/springschool.html It seems also a good summary of everything haskell-related :) Thanks, it is useful to me. Vincenzo ___ Haskell mailing list [EMAIL PROTECTED]

Re: AW: slide: useful function?

2002-12-02 Thread Andrew J Bromage
G'day all. On Mon, Dec 02, 2002 at 08:26:06AM +0100, Johannes Waldmann wrote: well I love design patterns, it's just that in Haskell-land they are called higher-order functions, or polymorphic functions, etc. Can I safely translate that as We use design patterns but we don't like the name?

Re: AW: slide: useful function?

2002-12-02 Thread Andrew J Bromage
G'day all. On Mon, Dec 02, 2002 at 10:27:21AM +0100, John Hughes wrote: There are patterns of that sort in our programs, which we would probably rather call design techniques, which aren't so easily captured by a higher-order function definition. As a matter of interest, _why_ would we

Re: AW: slide: useful function?

2002-12-02 Thread Andrew J Bromage
G'day all. On Mon, Dec 02, 2002 at 01:05:27PM -0500, David Bergman wrote: It seems like all the patterns, at least the ones in the GoF's enumeration, can be expressed as higher-order functions and classes if we only would have a way to traverse a record structure dynamically. If someone can

Re: AW: slide: useful function?

2002-12-02 Thread John Hughes
On Tue, 3 Dec 2002, Andrew J Bromage wrote: On Mon, Dec 02, 2002 at 10:27:21AM +0100, John Hughes wrote: There are patterns of that sort in our programs, which we would probably rather call design techniques, which aren't so easily captured by a higher-order function definition. As a

RE: Implementing forward refs in monadic assembler and interprete r

2002-12-02 Thread Simon Peyton-Jones
| For the moment I've chosen to do the mdo desugaring manually instead | of moving to the CVS ghc (or exclusively using Hugs.) Will mdo be in | the next release? (That's 5.04.2, I think -- though I've recently | been confused about GHC releases.) The relevant revision to Lex.lhs | is pretty

RE: Implementing forward refs in monadic assembler and interprete r

2002-12-02 Thread Ashley Yakeley
At 2002-12-02 00:37, Simon Peyton-Jones wrote: Main things in the next major release are mdo Template Haskell Can mdo be done in TH? It would be nice if there were some kind of macro system for this sort of thing; I know there's also a syntax for Arrows that requires a

RE: AW: slide: useful function?

2002-12-02 Thread Mark Carroll
On Mon, 2 Dec 2002, David Bergman wrote: (snip) Till then, we Haskellers will probably continue expressing our patterns either directly in Haskell or using highly formal language, with terms such as catamorphisms. The virtue, and weakness, of traditional design patterns is their vagueness