I am wondering if anyone has any 'standards' documents that they give
incoming programmers. If so I would like to get a copy (if not
proprietary) so I can smudge into a document we are creating here.
There have never been any standards documents and I would like to see
it here.

I am not really trying to start a discussion here (best for/next
etc .. or best editor but would like to see what people have.

I will be happy to make available any ending document we have
generated.

Thanks

"dtsig" <dtsig (AT) hotmail (DOT) com> wrote

<snip>

You should always use LOOP/REPEAT. Stay away from FOR/NEXT - it will only
cause grief.

And anyone who isn't using EditPlus for editing should be strung up.

Ed "Always trying to create trouble" Sheehan :-)

Every standards document I have seen in almost 40 years have always been the
same. Do this; don't do that. Well, do THIS means don't do THAT. So there
is only one standard:

Don't do anything we can't maintain when you're gone.


"dtsig" <dtsig (AT) hotmail (DOT) com> wrote

"dtsig" wrote:

This topic has been discussed a number of times here and usually leads
to very long threads, in-fighting, etc. Bottom line is, it is
whatever you say it is.

Search through Google groups.
Here is an example query for "coding standards":
<http://groups.google.com/groups?q=%22coding+standards%22+group:comp.databas es.pick>

Here are a couple examples of prior discussions:
http://tinyurl.com/2opekj (standards)
http://tinyurl.com/2qycp6 (programmer abilities)
http://tinyurl.com/3ylsro (what is good code?)
http://tinyurl.com/3aglly (preferred constructs)
http://tinyurl.com/35w3tx (good programming practices)
http://tinyurl.com/2qcarr (actual standards doc by Steve Alexander)
http://tinyurl.com/3bv2af (coding nightmares discovered during Y2K)
http://tinyurl.com/3yph6k (more commends on standards)

I hope that's a good start for ya.

T

On Feb 8, 2:53 am, Tony Gravagno
<g6q3x9lu53... (AT) sneakemail (DOT) com.invalid> wrote:
In the doc referred to above, where the following code is given...

*
400 * see if the trial is prime
*
PRIME = 1
IF TRIAL < 4 THEN RETURN
LIMIT = INT(SQRT(TRIAL)) + 1
FOR I = 2 TO LIMIT WHILE PRIME
IF NOT(MOD(TRIAL,I)) THEN PRIME = 0
NEXT I
RETURN

....change "FOR I = 2 TO LIMIT WHILE PRIME" to:
IF MOD(TRIAL,2) THEN
PRIME = 0
END ELSE
FOR I=3 TO LIMIT STEP 2 WHILE PRIME
and insert "END" after "NEXT I"

Also, it is a good idea to restrict subroutines to a single entry
point and a single exit point (RETURN statement) - hence the IF
THEN...END ELSE...END construct I employed rather than use another
RETURN statement. Following on from this, use CASE constructs rather
than:
IF...THEN
....
END ELSE
IF...THEN
....
END ELSE
IF...THEN
....
END
END
END

Mike.

http://tinyurl.com/3bv2af(coding nightmares discovered during
Y2K)http://tinyurl.com/3yph6k(more commends on standards)

On Feb 7, 5:02 pm, "dtsig" <d... (AT) hotmail (DOT) com> wrote:
My advice is "consistency before efficiency". It works for me and the
people that have worked for me. Two, three, four years down the road
you will see the results when you have to modify a program.
Modifications and enhancements will be a lot easier.

Here is one tip I learned from an old friend. If you are using a LOOP/
REPEAT use EXIT and CONTINUE see the following. It makes reading the
code easier for both entry level and seasoned programmers.

LOOP
READNEXT ID ELSE EXIT (takes you out of the LOOP/REPEAT)
READ R.REC FROM F.FILE, ID ELSE R.REC = ''
IF R.REC<5> = 'Y' THEN CONTINUE (skips down to the REPEAT and up
to the LOOP for the next ID)
......
......
REPEAT


BTW: I never use a LOOP/REPEAT UNTIL DONE DO! Some of these statements
could be confusion to follow.

Peter

On Feb 7, 6:53 pm, Tony Gravagno
<g6q3x9lu53... (AT) sneakemail (DOT) com.invalid> wrote:
It is funny .. i specifically said i didn't want to get into a
debate. If someone had a document cool .. if not .. then they should
have moved on.

On Feb 8, 2:53 am, Tony Gravagno
<g6q3x9lu53... (AT) sneakemail (DOT) com.invalid> wrote:
In the doc referred to above, where the following code is given...

*
400 * see if the trial is prime
*
PRIME = 1
IF TRIAL < 4 THEN RETURN
LIMIT = INT(SQRT(TRIAL)) + 1
FOR I = 2 TO LIMIT WHILE PRIME
IF NOT(MOD(TRIAL,I)) THEN PRIME = 0
NEXT I
RETURN


....change "FOR I = 2 TO LIMIT WHILE PRIME" to:
IF NOT(MOD(TRIAL,2)) THEN
PRIME = 0
END ELSE
FOR I=3 TO LIMIT STEP 2 WHILE PRIME
and insert "END" after "NEXT I"


Also, it is a good idea to restrict subroutines to a single entry
point and a single exit point (RETURN statement) - hence the IF
THEN...END ELSE...END construct I employed rather than use another
RETURN statement. Following on from this, use CASE constructs rather
than:
IF...THEN
....
END ELSE
IF...THEN
....
END ELSE
IF...THEN
....
END
END
END


Mike.


http://tinyurl.com/3bv2af(coding nightmares discovered during
Y2K)http://tinyurl.com/3yph6k(more commends on standards)

http://tinyurl.com/2qcarr

You're quite welcome. Moving on now.