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
> higher
> 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:
> >
> > $alp
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
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 b
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
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.
> 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 see
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 - ple
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 Unico
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 DateTim
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". We
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
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 poin
13 matches
Mail list logo
