Thanks, Bruno. Very educational.
rd
Bruno Desthuilliers wrote:
> Think of a class as both a "blueprint" for objects and a factory
> creating these objects. The class lets you define the attributes and
> behaviors of it's instances.
>> First, notice that you *don't* need a class here to avoid globals.
> Learning to use function as *functions* (ie: taking arguments and
> returning values) instead of procedure would help:
>> Now for an OO version - that won't buy you much IMHO:
>
