(no subject)

Title: Untitled Document ¾­¹ý´óÁ¿Ñо¿¹¤×÷£¬¼ÓÄôóÂê¿Æ˹ÆóÒµÓÐÏÞ¹«Ë¾ÍƳöÐÂÒ»´úÕÅÁ¦Òõ¾¥Ôö´óÆ÷¡£Ëü²»

Aladesc Launch

After two years in development Jalco Software Ltd is please to announce the launch of Aladesc - It's a Totally Fresh Outlook! Available in versions for the home and for business, Aladesc is an affordable Information and Communications Management System. If your business needs to share informat

CFP: 2002 Haskell Workshop ** submission deadline: 24th May **

[My apologies if you receive multiple copies of this message] --- C A L L F O R P A P E R S ** last call - submission deadline: 24th May ** --- ACM SIGPL

Re: Class Multiplicity

At 2002-05-18 00:41, Andrew J Bromage wrote: >Sometimes I think it would be handy if the Prelude used it more, >because then you could have full overloading for types which don't >quite play by the rules of the standard classes. For example: I do this sort of thing, see for instance:

Re: Class Multiplicity

G'day all. On Thu, May 16, 2002 at 11:48:58PM -0700, Ashley Yakeley wrote: > I have a curious Haskell design pattern. It's called "one class per > function". When used in conjunction with fundeps, I call it "hacking C++-style function overloading". Sometimes I think it would be handy if the P