> My point is mostly that stop() does not have any meaning It has the meaning of things being "stopped", not moving on their own anymore. Which sounds good to me, and it does not bring unwarranted meaning from other languages.
> Didn't we had a discussion recently about the fact you don't think it's > useful to formalize interfaces in duck-typed languages ? Sure, that has little to do with interface since there's behavior in these methods (namely setting and querying a flag). This behavior will often be extended (first and foremost in the parenting thing), but it still packs behavior which would have to be reimplemented in every "stoppable" type. > Xavier, you just criticize my solution I don't see it as a solution since I don't see any evidence of a problem to start with. > Can't you try to justify it? My justification is that there's no reason for it. Since you're *breaking* an existing interface the burden of the proof is on *you* do demonstrate this change brings more value than pain, and so far I have not seen anything even remotely close, you just decided you wanted to change it. -- https://code.launchpad.net/~openerp-dev/openerp-web/trunk-core-extraction-1-niv/+merge/94021 Your team OpenERP R&D Team is subscribed to branch lp:~openerp-dev/openerp-web/trunk-core-extraction-1-niv. _______________________________________________ Mailing list: https://launchpad.net/~openerp-dev-gtk Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-dev-gtk More help : https://help.launchpad.net/ListHelp
