In <105438.15379...@web161401.mail.bf1.yahoo.com>, on 05/15/2011
at 09:47 PM, Ed Gould <ps2...@yahoo.com> said:
>People write in whole complete sentences for a complete thought
>to be conveyed.
Some people do, sometimes. Some people sometimes write perfectly
understandable sentence fragments.
>Take as an example (sorry do not
>have the number off the top of my head). I believe its called the
>MVS COBOL conversion guide (or something close) is close to what I
>am trying to convey here. They manage to take a simple statement
>and turn into a legalize length document that you truly have to be
>a lawyer to understand.
If you didn't understand it, how do you know that it is equivalent to
a simple statement? I agree that there is verbose text in some
manuals, but there are also cases where what the text describes is
complex and a shorter description would be flat wrong.
>Some of the replies on here are a lot like that.
Certainly. But have you correctly determined which are which? I'd
rather wade through complex text than make a programming error as the
result of believing an overly simplistic post.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
