Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Programming > Forth > Re: Writing, Co...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 1 of 1 Topic 3926 of 4136
Post > Topic >>

Re: Writing, Coding, and Professionals

by Bruce McFarling <agila61@[EMAIL PROTECTED] > Mar 18, 2008 at 05:18 PM

On Mar 18, 4:41 pm, "Paul E. Bennett" <Paul_E.Benn...@[EMAIL PROTECTED]
>
wrote:
> Anton Ertl wrote:
> > Guy Macon <http://www.guymacon.com/>
writes:
> >>A good programmer writes his/her comments in such a way that
> >>a far better programmer could, in theory, start with just the
> >>comments and end up with a working program that does the same
> >>basic job that the original program does.

> > You want the complete specifications in the comments.

> > For most programs a complete specification is never written, so it
> > would certainly be an improvement if it was.  However, I don't see why
> > it should be in the comments.  Ok, an advantage would be that it would
> > be more likely to be updated when the requirements change (rather than
> > just updating the code).  But OTOH interspersing the spec with code
> > and structuring it in the same way as the code makes it harder to
> > understand.

> When decomposing the functions towards the words you will use in the
> application it can be beneficial to write the glossary for the words
> (and reviewing the glossaries) long before you get to write the code
> that sup****ts that functionality.

> Ensuring that these glossary comments are traceable to and from the
> original specification and that the code, when written, fully sup****ts
> the glossary spec for the word is the foundation for certifying the code
> compliant with the requirements. If you can then prove the codes
> robustness by arduous testing you can gain a high degree of confidence
> in the dependability of the system.

> This might be as close as anyone gets to fully specified software.

Yes, this is what the -[ --[ and ---[ block comments are intended to
sup****t.

A section of code can be:

--[ section title ]--

glossary goes here

\ comment line

code goes here

--[ next section title ]--

.... keeping the glossary in small, closely related chunks, in front of
the code that should follow those semantics.

It sup****ts splitting off the code ****tion for a target that needs the
script but have very tight storage space ... but is primarily intended
to be interpreted as-is.
 




 1 Posts in Topic:
Re: Writing, Coding, and Professionals
Bruce McFarling <agila  2008-03-18 17:18:00 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Wed Jul 9 5:52:21 CDT 2008.