To be or not to be inherited

[TylerH]

This is a rather simple poll.

 

1. Self explanatory.
2. Basically means core stuff, such as the math entities' abilities to store numbers is core, and the specific entities manipulate it certain ways, i.e. math_base adds the ability to story a "value" key, math_add has the ability to add to it, math_subtract has the ability to subtract from it.
3. For the LOLs.
4. Sort of for the LOLs, or for people who think they are smarter than me.

[Canardia]

I voted for option 2, it sounds like less duplicate code, and easier maintenance.

Although I think that intelligence is too slow for modern needs, and that intuition replaces it completely (referring to your option 4 comment).

[TylerH]

Yes, my intuition lead me to vote for Option 2.

 

Good to see we agree. That alone is enough for me to decide to go with it, unless someone else provides an argument that can debunk intuition.

[Josh]

There are other ways of doing inheritance, but my function renaming approach seemed the simplest to understand. One consideration was that if I was having trouble understanding table inheritance, many of my users would too, and that would have a negative impact on their experience and my sales.

[TylerH]

That is surprising. The inheritence in Lua is rather easy, if not, then Garry's Mod does hell of a good job at it.

 

I would recommend e-mailing garrynewman [at] gmail [dot] com and asking him how he set it up. In fact, I will do the same, too. He is usually quick to respond to professionals (non-12 year olds who know what they are speaking about), though he tends to swear a bit if you come off wrong.

[Josh]

Lua inheritance seems extremely workaroundish to me:

http://lua-users.org/wiki/InheritanceTutorial

[TylerH]

http://apache.dataloss.nl/~peter/www.lua.org/pil/

 

Chapters 15,16,17 are excellent. They taught me loads of new stuff I didn't know about.

 

You can change the environment (kind of like a new lua state) by calling setfenv(1, { })

 

Look into it, it is very promising. Those chapters describe everything from namespaces, to protoyping, inheritence, full OO patterns, weak tables, etc.