[E-Lang] a small evolution in the "class" convention

[Marc Stiegler]

In earlier email, I proposed that in Walnut I would be using the following
convention:

class Thing() :any {
    def thing { }
}

def thing := Thing new()

Talking with markm, he pointed out that the token "Thing" in the above
example needs to be replaced with thingMaker (or ThingMaker, I will go with
thingMaker, which is the way it is now) because the token Thing really needs
to be reserved for usage as the type (or the guard, for E objects). So for
those of you eager to know what it is going to look like in the next version
of Walnut (which now needs a massive overhaul because of all the
improvements we have made in the last week...man, I hate it when things get
this much better), it will look like this:

class thingMaker() :any {
    def thing {}
}

def thing := thingMaker new()

Anyone who is really excited about this can discuss it with markm :-)

--marcs