Ticket #18 (closed enhancement: fixed)

Opened 11 months ago

Last modified 11 months ago

Switch from class-based OO to prototype-based OO

Reported by: JarrettBillingsley Assigned to: JarrettBillingsley
Priority: major Milestone: MiniD 2
Component: Language Keywords:
Cc:

Description

Rather than classes and instances, just have objects. Clone them to "instantiate" or to subclass. More dynamic and less complex.

I'm still kind of out on this one. I've got a lot of the proto-based code written (pretty much everything except supercalls, which become a bit tricky), but I don't know.. the more I think about it the more I wonder if it's really worth it, and it'll do nothing but make the binding library more complex.

Change History

01/15/08 21:18:37 changed by JarrettBillingsley

  • component changed from component1 to Language.

01/15/08 22:24:09 changed by JarrettBillingsley

  • status changed from new to closed.
  • resolution set to fixed.

Well I've had a change of heart in favor of proto-based. I like it, and it turns out not to be that big of an issue mapping native objects to it.

It's implemented now, and the stdlib classes have been converted over to proto OO. Which means it's done.