🚀 go-pugleaf

In article <ROCKWELL.92Apr8151628@socrates.umd.edu> rockwell@socrates.umd.edu (Raul Deluth Miller-Rockwell) writes:
> In a sense, this is true, but I think it misses a big issue:  there is
> a major distinction between 'type' and 'storage class'.

Sure is. And you're confusing things again...

> 'storage class' is a concept used when talking about the machine
> representation of data.

No, it's used when talking about the lifetime of data, as opposed the scope
which refers to the lifetime of an identifier. For example, objects created
on the stack in a conventional programming language have a lifetime limited
to the duration of that stack frame. Two different machine types (what you're
referring to as storage classes) may have the same storage class. For example:

	int foo(void)
	{
		int a;
		double b;
	}

The variable a has machine type "int", type "integer", scope "block",  and
storage class "automatic".

The variable b has machine type "double", type "floating point", scope "block",
and storage class "automatic"

	      SUBROUTINE FOO
	      INTEGER A
	      REAL*8 B
	      END

Here A and B have storage class "static" and scope "function".
-- 
/F{findfont exch scalefont setfont}def /S{moveto show}def /T{/Times-Roman F}def
8 T(Ferranti International Controls Corporation)24 28 S(+1 713 274 5180)24 12 S
(Sugar Land, TX  77487-5012)24 20 S 12 /Courier F(`-_-')320 32 S( 'U` )320 16 S
12 T(Peter da Silva)24 36 S 16 T(Have you hugged your wolf today?)358 24 S