🚀 go-pugleaf

In article <4255@utah-cs.UUCP> shebs@utah-cs.UUCP (Stanley Shebs) writes:
>In article <277@figaro.STANFORD.EDU> asente@figaro.UUCP (Paul Asente) writes:
>
>>... advocates of
>>totally untyped systems (like Smalltalk) always dredge up the example of
>>having a queue (or stack or list...) that allows arbitrarily mixed
>>data to be enqueued.  In all my years of programming I have never wanted
>>to do anything like this.
>
>If you've ever used a variant record in Pascal or pointer tricks in C or
>equivalences in Fortran, you've wanted polymorphism.  If you've ever used
>numbers in specified ranges as tokens with various meanings, you've wanted
>polymorphism

...following are many good examples of why you want polymorphism.

In case it wasn't clear from my original posting, it is not polymorphism
that I find questionable, it's unbounded polymorphism.  In each of the
examples in Stanley Shebs' article, you are chosing a type out of
a limited set that you know beforehand.  Even Simula allows that, and
it can be appropriately type-checked.  What I find of dubious usefulness
and even more dubious stylistic practice even if it were useful is
creating a data structure having no idea of what goes into it.  Can
you actually think of an example where you would want a queue that
allowed you to enqueue absolutely anything?  If you know what's going in,
it may be more convenient to program it with no element type checking
than to set up subtypes of the queue elements for the types you know
are going in, but is it really good style?

Of course, "style" is about the vaguest word you can use to describe
a program.  What I mean by style is the degree that the program can
be understood and modified by someone unfamiliar with it.  This of
course may well be the author, two years later.

One final point...if you REALLY need a queue with anything in it,
languages like CLU allow you to sidestep the type system by using
a predefined type that is the union of all types.  But you don't
have to sacrifice the advantages of compile-time type checking
for this one obscure instance.

	-paul asente