Re: ghc-pkg 6.2 incorrectly parses commas within quotes

2004-02-16 Thread Sven Panne
Ashley Yakeley wrote: Any word on whether this has been/will be fixed? [...] Well, it's fixed in CVS for quite a while, but it's up to Simon^2 when a new GHC release comes out. Personally I'd favour tossing this feature altogether, [...] Me too... :-P * * * Cheers, S.

Re: ghc-pkg 6.2 incorrectly parses commas within quotes

2004-02-16 Thread Sven Panne
Ashley Yakeley wrote: Any word on whether this has been/will be fixed? [...] Well, it's fixed in CVS for quite a while, but it's up to Simon^2 when a new GHC release comes out. Personally I'd favour tossing this feature altogether, [...] Me too... :-P * * * Cheers, S.

Re: [Haskell] 3d or Nd geometry library?

2004-02-16 Thread Axel Simon
On Fri, Feb 13, 2004 at 11:31:39AM -0800, Abraham Egnor wrote: I was somewhat surprised to see that there's only one geometry library on the haskell libraries page, and further dismayed to find that it for the most part only does 2d. It seems like haskell should be a natural fit for

RE: [Haskell] non-ASCII characters in Haddock documentation

2004-02-16 Thread Simon Marlow
Am Freitag, 13. Februar 2004 01:23 schrieben Sie: wolfgang: Hello, how do I insert non-ASCII and maybe even non-Latin-1 characters in Haddock documentation? Wolfgang Looks like it might be difficult. The haddock lexer src has: $alphanum = [A-Za-z0-9] So,

[Haskell] Re: exists keyword and existential types

2004-02-16 Thread Ashley Yakeley
In article [EMAIL PROTECTED], Ben Rudiak-Gould [EMAIL PROTECTED] wrote: And it would be nice to be able to pass around values of type (exists t. Interface t = t), which behave just like OOP interface pointers. A value of type (exists t. Interface t = t) consists of two values, one of type

Re: [Haskell] non-ASCII characters in Haddock documentation

2004-02-16 Thread Ross Paterson
On Mon, Feb 16, 2004 at 10:20:30AM -, Simon Marlow wrote: Wolfgang Jeltsch [EMAIL PROTECTED] writes: I meant non-ASCII characters in source code comments like this: {-| The execution time of this function is /n³/. -} Currently, Haddock seems to copy the bytes making

Re: [Haskell] non-ASCII characters in Haddock documentation

2004-02-16 Thread Ketil Malde
Ross Paterson [EMAIL PROTECTED] writes: It shouldn't be too hard to fix this, at least for Latin-1 (full Unicode would be somewhat harder). I'll add it to the TODO list. While Haskell's source charset is specified as Unicode, Haskell source files don't specify the byte encoding they use, so

Re: [Haskell] non-ASCII characters in Haddock documentation

2004-02-16 Thread Ross Paterson
On Mon, Feb 16, 2004 at 12:51:06PM +0100, Ketil Malde wrote: Ross Paterson [EMAIL PROTECTED] writes: While Haskell's source charset is specified as Unicode, Haskell source files don't specify the byte encoding they use, so any source file using non-ASCII characters isn't portable.

RE: [Haskell] non-ASCII characters in Haddock documentation

2004-02-16 Thread Simon Marlow
On Mon, Feb 16, 2004 at 10:20:30AM -, Simon Marlow wrote: Wolfgang Jeltsch [EMAIL PROTECTED] writes: I meant non-ASCII characters in source code comments like this: {-| The execution time of this function is /n³/. -} Currently, Haddock seems to copy the

[Haskell] Wiki manager change

2004-02-16 Thread Keith Wansbrough
Hi all... the Haskell Wiki http://haskell.org/hawiki/ is under new management. From now on, please contact Shae Erisson [EMAIL PROTECTED] with your requests, comments, or feedback on the Wiki site - or, of course, improve and extend the site yourself! Thanks all for your contributions -

Re: [Haskell] non-ASCII characters in Haddock documentation

2004-02-16 Thread Graham Klyne
At 11:29 16/02/04 +, Ross Paterson wrote: On Mon, Feb 16, 2004 at 10:20:30AM -, Simon Marlow wrote: ... It shouldn't be too hard to fix this, at least for Latin-1 (full Unicode would be somewhat harder). I'll add it to the TODO list. While Haskell's source charset is specified as

[Haskell] updating graphs non-destructively

2004-02-16 Thread S. Alexander Jacobson
In imperative languages, updating an object in a graph is an O(1) operation. However, non-destructive update appears to be O(n) with the size of the graph. For example, suppose we were to implement an auction system like eBay: --Data structures data Bid = Bid BidId Auction User Price

[Haskell] Re: Data.Set whishes

2004-02-16 Thread Wolfgang Jeltsch
Am Montag, 16. Februar 2004 10:05 schrieb Ketil Malde: Wolfgang Jeltsch [EMAIL PROTECTED] writes: * subsetOf :: Ord element = Set element - Set element - Bool (Isn't isSubsetOf a better name?) So is isElementOf. I just said subsetOf to be consistent with elementOf. Well, the naming in

[Haskell] Re: exists keyword and existential types

2004-02-16 Thread Ben Rudiak-Gould
On Mon, 16 Feb 2004, Ashley Yakeley wrote: A value of type (exists t. Interface t = t) consists of two values, one of type t, and one dictionary value. For that reason a data type is used to represent this (and a newtype type cannot be). This is an implementation detail, though. It's like a

Re: [Haskell] updating graphs non-destructively

2004-02-16 Thread Tom Pledger
S. Alexander Jacobson wrote: In imperative languages, updating an object in a graph is an O(1) operation. However, non-destructive update appears to be O(n) with the size of the graph. For example, suppose we were to implement an auction system like eBay: [snip] One alternative is to store