No registered users in community xowiki
in last 10 minutes
in last 10 minutes
Re: [Xotcl] "tie" command
From: Gustaf Neumann <neumann_at_wu-wien.ac.at>
Date: Fri, 24 Jan 2003 16:54:15 +0100
On Friday 24 January 2003 15:44, Kristoffer Lawson wrote:
> On Fri, 24 Jan 2003, Gustaf Neumann wrote:
> > we could provide an option -bind <varname> to the new instproc to allow
> > the user to specify a local or a per-object or global variable name, but
> > this does not provide reference counting at all. i have started some
> > time ago
>
> Oh, I meant to say that an option to [new] is not necessarily the best.
> Often (at least in my case) it is a method of an object which creates
> an instance and returns it, like:
>
> set msg [$cmdReader getNewMessage]
>
> So at the level where I want the automisation I don't directly call new.
> Naturally this could be changed to accommodate the use of new, but then
> my interface wouldn't be as cleanly split up.
i don't get your point: getNewMessage has to create the Object,
so it can use certainly new (with all variants). is your argument:
the caller of newmessage should decide, whether the created
object should be dynamically reclaimed or not?
anyhow, it is not hard to do it one or the other way....
-gustaf
Date: Fri, 24 Jan 2003 16:54:15 +0100
On Friday 24 January 2003 15:44, Kristoffer Lawson wrote:
> On Fri, 24 Jan 2003, Gustaf Neumann wrote:
> > we could provide an option -bind <varname> to the new instproc to allow
> > the user to specify a local or a per-object or global variable name, but
> > this does not provide reference counting at all. i have started some
> > time ago
>
> Oh, I meant to say that an option to [new] is not necessarily the best.
> Often (at least in my case) it is a method of an object which creates
> an instance and returns it, like:
>
> set msg [$cmdReader getNewMessage]
>
> So at the level where I want the automisation I don't directly call new.
> Naturally this could be changed to accommodate the use of new, but then
> my interface wouldn't be as cleanly split up.
i don't get your point: getNewMessage has to create the Object,
so it can use certainly new (with all variants). is your argument:
the caller of newmessage should decide, whether the created
object should be dynamically reclaimed or not?
anyhow, it is not hard to do it one or the other way....
-gustaf
-- Univ.Prof. Dr.Gustaf Neumann Abteilung für Wirtschaftsinformatik WU-Wien, Augasse 2-6, 1090 Wien