🚀 go-pugleaf

>>		    List = RECORD CASE Null:BOOLEAN OF
>>				 TRUE:                |
>>				 FALSE:  Key: ... ;
>>					 Data: ... ;
>>					 Next: List
>>                           END;
>>

While the above type would indeed be infinite in the sense that
some of its ''possible'' values would be infinite, some of its
values would also be finite.  The problem is that the size of a 
value of such a type would not in general be determinable at 
compile time.  This implies automatic allocation of dynamic
storage, and that would break Modula-2 ... which has no garbage
collection.  A more sensible implementation would use hidden pointers
(hence the sizes would be determinable at compile time), but that
would still require garbage collection.  

BTW-1: It is not at all hard to distinguish at compile time between 
infinite types that are useful and those that are non-useful; i.e. 
those for which all values are infinite.

BTW-2: There ARE languages that allow infinite types; e.g. ML.

BTW-3: There ARE languages in which infinite types are represented 
without pointers; e.g. Courier and ANS 1.  Of course, these are not 
programming languages but languages for defining application level
communication protocols.  

-- Steve