Unfortunately, putting a good AI engine in Squeak may defeat the purpose of
reducing the image size. But that may be what's required to infer the param
names from the compiled code. t1, t2, etc. show up when a decompiler
generates Squeak code from the compiled method, in case the source code is
not available (e.g., if you abandoned source/changes files or in some cases
of doIts).

All implementors of #at:put: use intuitive names for the params.

Bolot

----- Original Message -----
From: "Sebastien Thoos" <ethiobite at bluewin.ch>
To: <squeak at cs.uiuc.edu>
Sent: Monday, December 13, 1999 12:41 PM
Subject: Calling things by their name.


> Hello,
>
> A question ....
>
> Why giving bizare names to parameters,
> when I say bizare I mean t1, t2, t3.
>
> It would be much more readable and make more
> sense to have a method called, for example:
>
> put: anObject at: aPosition
>
> I think we still can change things...
>
> SÈbastien.
>
>
>