[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: From Lua to Python?
- From: steve donovan <steve.j.donovan@...>
- Date: Thu, 13 Jul 2017 17:57:24 +0200
On Thu, Jul 13, 2017 at 3:48 PM, Dibyendu Majumdar
<mobile@majumdar.org.uk> wrote:
> Actually OO is essential tool for organizing large code bases. I am
> not talking about inheritance and all - but just the ability to
> organize your code into objects of different types. Remember objects
> carry state.
We used to do that in C just fine ;) It's a useful set of ideas, but
when it becomes a dogma and its meaning gets fossilized into whatever
the 'class' statement does, then it ceases to be so useful and spawns
its own pathologies, like the 'fragile base class problem' etc.
I've noticed this issue play out with Rust, which also does not have a
'class' concept. People have to wake up from their OO slumbers and
remember important distinctions between interface and implementation
inheritance etc.
This can easily stray too far from our topic, but I'm happy that Lua
does not have a class keyword. I learned that closures are so often
what we need.
- References:
- Re: From Lua to Python?, Dibyendu Majumdar
- Re: From Lua to Python?, Dibyendu Majumdar
- Re: From Lua to Python?, Dirk Laurie
- Re: From Lua to Python?, Dibyendu Majumdar
- Re: From Lua to Python?, Javier Guerra Giraldez
- Re: From Lua to Python?, Dibyendu Majumdar
- Re: From Lua to Python?, Enrico Colombini
- Re: From Lua to Python?, steve donovan
- Re: From Lua to Python?, Javier Guerra Giraldez
- Re: From Lua to Python?, steve donovan
- Re: From Lua to Python?, Dibyendu Majumdar