Design Discussion: Classes and Instances

JAPL is an object oriented language, so at some point we'll implement classes.

Specifically, I'd like to have:
- "magic" methods (a la Python) for built-in behavior like string representation or operator behavior (`magic method toString() {...}`)
- abstract classes and methods (`abstract class` and `abstract method`)
- Multiple inheritance like so: `class Child < Parent1, Parent2 {}`. Layout conflicts are resolved at compile time
- `static` methods (i.e. not bound to an instance)
- Private Fields? (and methods maybe). I kinda have to figure this one out

Anything else?

No files, tests, or entry points are identified in this issue. Begin by reviewing the JAPL language implementation and establish an agreed, implementable scope for classes and instances; done is a settled design rather than a completed patch.

Written by the indexing model from the issue text.