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.
>Richard,
> In each of the cases you cite, wouldn't it be simpler
>and clearer just to replace asserts with signals?
>for example: The bus controller signals Data Ready .....
>Jan
>------------
> The bus controller asserts Data Ready for as long as the data on D0-D7 is
> stable.
> The bus controller asserts Data Ready for 10ns when the data on D0-D7
> becomes stable.
> The bus controller asserts Data Ready when the data becomes stable, then
> removes it when the data lines no longer contain valid data. ...RM
I think using 'signals' is more abstract. To me the term 'asserts' holds a
specific meaning; in this case, the controller sets the Data Ready line
true.
That it 'signals' Data Ready confuses me because:
Data Ready *is* a signal,
who/what does it signal to, and
Signal doesn't necessarily indicate action.
