Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!hplabs!hpfcso!hpfelg!koren
From: koren@hpfelg.HP.COM (Steve Koren)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Anybody know how to do this stuff?
Message-ID: <13920023@hpfelg.HP.COM>
Date: 4 Dec 89 01:59:29 GMT
References: <13920020@hpfelg.HP.COM>
Organization: HP Elec. Design Div. -FtCollins
Lines: 26

> Do you have a counterexample?  It sounds a lot like you are setting
> titles for windows you do not own and then exiting, or otherwise
> treading dangerously on thin ice.

Well, this point is a little unclear to me.  Who "owns" the CLI window?
Is the the currently running shell?  What if a shell is invoked from
within a shell?  I wished to add a command which lets the user change
the window title bar of the CLI window by saying something like:

     window -title "my title"

I wanted to implement this command as an external binary.  The binary
sets the window title and then exits.  Perhaps that is not a legal thing
to do, in which case I'll leave the command out.

It is probably a bit late for this now, but it is my belief (just opinion
here) that a child procedure should not depend on dynamically allocated data
passed to it hanging around after the child exits.  If it needs the data,
it should copy it.  Having it depend on the data's persistance increases
coupling strength between the two procedures, which is generally regarded
as a "bad thing" in software engineering circles.  (Of course, I do this
sometimes myself :-)

Anyhow, thanks for the help.

    - steve