Re: Replacing "master" and "slave" terminology

[John Hedtke <john -at- hedtke -dot- com>]

I'd vote against parent/child simply because it is a standard in 
OOP.  Reusing terminology runs a greater risk of confusing people.




At 01:40 PM 4/10/2008, Evelyn Lee Barney wrote:


>Paul,
>
>I have to say this is the only alternative I've heard that I thought
>worked.  Like others on this list, I felt stuck with master/slave for
>clarity reasons.  However, as parent/child is a common term in
>object-oriented programming, I bet this could catch on easily enough.
>
>Ev

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Create HTML or Microsoft Word content and convert to Help file formats or 
printed documentation. Features include support for Windows Vista & 2007 
Microsoft Office, team authoring, plus more.
http://www.DocToHelp.com/TechwrlList

True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to 
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/ for more resources and info.