Re: User-Defined Operators (ad-hoc overloading)

2003-07-22 Thread Christian Maeder
Andrew J Bromage wrote: As a matter of interest, is there a known worst-case complexity for the precomputation required by Earley's algorithm to handle arbitrary CFGs? Earley's algorithm handles exactly arbitrary (in particular ambiguous) CFGs without precomputation. see i.e. Aho,Ullman, The

Re: User-Defined Operators (ad-hoc overloading)

2003-07-21 Thread Christian Maeder
Mere overload resolution (over monomorphic types) is not NP-hard. (This is only a common misconception.) I can only repeat my above sentence. No, but as you note below, the interesting cases are. Most of the more interesting number-like types are polymorphic (e.g. Complex, Ratio). This kind of

Re: User-Defined Operators (ad-hoc overloading)

2003-07-21 Thread Andrew J Bromage
G'day all. On Mon, Jul 21, 2003 at 01:07:39PM +0200, Christian Maeder wrote: Mere overload resolution (over monomorphic types) is not NP-hard. (This is only a common misconception.) I can only repeat my above sentence. I'm a firm believer in the maxim that the best way to find information

Re: User-Defined Operators (ad-hoc overloading)

2003-07-18 Thread Christian Maeder
Andrew J Bromage wrote: Of course you could always allow overloading _without_ requiring module qualification (unless the overloading can't be resolved using type information). It'd make type checking NP-hard, but I seem to recall that it's already more complex than that. Mere overload resolution

Re: User-Defined Operators (ad-hoc overloading)

2003-07-18 Thread Andrew J Bromage
G'day all. On Fri, Jul 18, 2003 at 11:08:16AM +0200, Christian Maeder wrote: Mere overload resolution (over monomorphic types) is not NP-hard. (This is only a common misconception.) No, but as you note below, the interesting cases are. Most of the more interesting number-like types are