lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

100% agreed.

Lua doesn't need a standard 'class' system. There is the danger of locking people into it (a mild danger) but there is also the danger of bringing in things that are not necessary to many people.

If something is going to change in this direction, it will probably be one of those clever devices one of the Three Creators sometimes devise to solve a thousand problems with some simple concept, a handful of code and almost no overhead ;-).

OOP is just too messy, too complex a problem to fit this definition. It should be a *use recommendation*, not a language construct. And s such, should come in several flavors.

On Jan 14, 2008 7:29 PM, Javier Guerra <> wrote:
my two cents:

- most 'quick & dirty' programs doesn't need OOP

- the obj:mth() syntactic sugar trivially handles encapsulation and polymorphism

- most OOP simple (and not so simple!) designs doesn't need inheritance.

- if you need a full inheritance class system, there are several to
pick from. some of them really sophisticated.

- no matter how a class system is implemented, if it uses the
obj:mth() sugar for method calls, it can interoperate with other

so.... why the fuss?


Luís Eduardo Jason Santos