RE: Documenting program flow

Subject: RE: Documenting program flow
From: Andrew Warren <awarren -at- synaptics -dot- com>
To: "salt -dot- morton -at- gmail -dot- com" <salt -dot- morton -at- gmail -dot- com>, "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Fri, 9 Jan 2015 21:56:15 +0000

Chris Morton wrote:

> These are not commands, per se. What are they called in documenting
> program flow control... *operatives*?

"Statements". Or, notwithstanding your assertion, "commands".


=== Andrew Warren - awarren -at- synaptics -dot- com
=== Synaptics, Inc - San Jose, CA
Doc-To-Help: The Quickest Way to Author and Publish Online Help, Policy & Procedure Guides, eBooks, and more using Microsoft Word |


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-leave -at- lists -dot- techwr-l -dot- com

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

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @

Documenting program flow: From: Chris Morton

Previous by Author: RE: Economist magazine points to decline of tech writing
Next by Author: RE: Upload versus download
Previous by Thread: Re: Documenting program flow
Next by Thread: Reality check: "mS" time increment?

What this post helpful? Share it with friends and colleagues:

Sponsored Ads