[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: OOP flavours
- From: Asko Kauppi <asko.kauppi@...>
- Date: Sun, 16 Jan 2005 13:45:37 +0200
But there could be many.
require "obj_adams" :)
The point being, instead of building a whole system from the ground up
(and doing all the mistakes) a newcomer could simply pick-and-place the
one system she wants. And even, if these packages were centrally
orchestrated, their API approaches could be at least similar to each
Some document could then be used to highlight the differences &
pros/cons of each of them.
16.1.2005 kello 12:23, Adam D. Moss kirjoitti:
Personally I think that self.something() / self.super.something()
is clearer than 'something' implicitly coming out of the class's
namespace. A standardised object mechanism isn't likely to address
such personal preferences.