RE: incomplete datatyping (was: Re: datatypes and MT)

>Thanks for the info.
>
>This actually makes the example of the size property
>even more meaningful, as it shows the ambiguity even
>more clearly. Since there is no single derived type
>"responsible" for disambiguation, there is no explicit
>means to decide *which* range should be used to interpret
>the non-locally typed literal.

True, but this seems to be a general problem with any datatyping 
scheme, even the URV idea. If I use a URV with a 'unioned' type name, 
something has to be able to fit the right part of the datatype 
mapping with the particular lexical form it finds itself combined 
with. God help us if we allow a union of decimal and octal.

Pat


-- 
---------------------------------------------------------------------
IHMC					(850)434 8903   home
40 South Alcaniz St.			(850)202 4416   office
Pensacola,  FL 32501			(850)202 4440   fax
phayes@ai.uwf.edu 
http://www.coginst.uwf.edu/~phayes

Received on Thursday, 8 November 2001 19:12:01 UTC