Dieter Maurer <[EMAIL PROTECTED]> wrote:
> I think an additional reason for the "_" in the name of
> "_setObject" is to prevent acquisition.
>
> With acquisition, you may not set the object where you think you will.
Ah, that's a very good argument.
(Another reason why implicit acquisition is ba
Leonardo Rochael Almeida wrote at 2003-2-3 18:42 -0200:
> ...
> Let's not confuse this with TTW public methods. _setObject should
> obviously not be made TTW accessible (let alone TTW public :-), but it
> should be a "public" method, that is, have a sensible name and be
> specified in an event
On Sat, 2003-02-01 at 12:16, Max M wrote:
> Lennart Regebro wrote:
> > From: "maxm" <[EMAIL PROTECTED]>
> >
> >>Usually a private method is used purely as a mean of implementation. And
> >>should never be called from other objects. This is not the case here, as
> >>the method is clearly a part of
Lennart Regebro wrote at 2003-2-1 15:48 +0100:
> From: "Max M" <[EMAIL PROTECTED]>
> > Sorry but I don't see that. How on earth are you suposed to add an
> > object to an objectmanager, if you don't use _setObject() ??
>
> You use another method that in turn calls _setObject.
>
> Now you m
maxm <[EMAIL PROTECTED]> wrote:
> I have a few tutorials / How_to's on zope.org. And sometimes I get some
> interresting mails because of that.
>
> Somebody asked me today why _setObject() has that name, as it is used in
> many products, and thus ought to be an interface method. And called
> s
From: "Max M" <[EMAIL PROTECTED]>
> Sorry but I don't see that. How on earth are you suposed to add an
> object to an objectmanager, if you don't use _setObject() ??
You use another method that in turn calls _setObject.
Now you may argue that there should be a public method that does the same,
bu
Lennart Regebro wrote:
From: "maxm" <[EMAIL PROTECTED]>
Usually a private method is used purely as a mean of implementation. And
should never be called from other objects. This is not the case here, as
the method is clearly a part of the api.
Well, no, it isn't really, since it starts with _.
From: "maxm" <[EMAIL PROTECTED]>
> Usually a private method is used purely as a mean of implementation. And
> should never be called from other objects. This is not the case here, as
> the method is clearly a part of the api.
Well, no, it isn't really, since it starts with _. However, python do no
Dieter Maurer wrote:
> "_setObject" has an "_" because it is a "private" method
> which should not be called by TTW code.
Ok ... but that is not really what is meant by a private method.
Usually a private method is used purely as a mean of implementation. And
should never be called from other o
maxm wrote at 2003-1-31 00:35 +0100:
> I have a few tutorials / How_to's on zope.org. And sometimes I get some
> interresting mails because of that.
>
> Somebody asked me today why _setObject() has that name, as it is used in
> many products, and thus ought to be an interface method. And ca
10 matches
Mail list logo
