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.
Years ago I wrote a manual documenting a report generation program that
used BNF. There was, as had been said, no
source so I had to learn it from scratch. I am attempting to obtain a
copy of that manual. If I am successful, I will contact you.
> -----Original Message-----
> From: Scott McClare [SMTP:smcclare -at- DY4 -dot- COM]
> Sent: Thursday, July 30, 1998 2:05 PM
> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
> Subject: Re: Command Notation
>> -----Original Message-----
> >> From: Anne Weiner [SMTP:annew -at- INTERDYN -dot- COM]
> >>Sent: Wednesday, July 29, 1998 9:33 PM
> >> Subject: Command Notation
> >>Lo these many years I was involved in a project whereby a command
> >>was documented. I remember that in the planning stage we discussed
> >>different alternatives for notation, one was "railroad diagramming"
> >>think), the other was a hyphenated term which I have completely
>It looks to me like you're thinking of the "Backus-Naur"
>not aware of any print reference that documents it (perhaps
>on the list can enlighten all of us!), but maybe you can glean
>from the BNF entry in the Jargon File: