TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Re: I need help with Functionality versus Function ; Plus
Subject:Re: I need help with Functionality versus Function ; Plus From:"Huber, Mike" <mrhuber -at- SOFTWARE -dot- ROCKWELL -dot- COM> Date:Wed, 15 Jul 1998 15:23:50 -0400
Also, "Function" has a very specific meaning for programmers. A function is
a software thingie that returns a value.
You use a function, you get an answer. Often, the answer is just "Yup, did
it, no problem" but no answer, no function.
It's not a trivial distinction. Trust me on this - your programmers, or, if
you write for programmers, your customers, care deeply whether a particular
functionality is a function or not.
---
Office:
mike -dot- huber -at- software -dot- rockwell -dot- com
Home:
nax -at- execpc -dot- com
> -----Original Message-----
> From: Mark Baker [SMTP:mbaker -at- OMNIMARK -dot- COM]
> Sent: Wednesday, July 15, 1998 12:15 PM
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: Re: I need help with Functionality versus Function ; Plus
>
> Mark Dempsey wrote
...
> To address the original question: "Functionality" describes the behavior
> of
> the whole. "Functions" describes the behavior of the parts. These are
> different things requiring different names.
>
