@listserver.u2ug.org
Sent: Sunday, October 02, 2005 4:59 AM
Subject: Re: [U2] Good Programming Practice Question.
Mark Johnson [EMAIL PROTECTED] wrote on 10/01/2005 01:00:33
AM:
Files that can't open are usually solved pretty quickly either after
installing the software or making the changes
Mark Johnson [EMAIL PROTECTED] wrote on 10/01/2005 01:00:33
AM:
Files that can't open are usually solved pretty quickly either after
installing the software or making the changes. The downstream elaborate
errmsgs for
OPEN CUSTOMER TO F.CUSTOMER ELSE PRINT CANNOT OPEN THE CUSTOMER FILE.
Message -
From: Timothy Snyder [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Sunday, October 02, 2005 4:59 AM
Subject: Re: [U2] Good Programming Practice Question.
Mark Johnson [EMAIL PROTECTED] wrote on 10/01/2005 01:00:33
AM:
Files that can't open are usually solved
of the
rules while others allow to do whatever the developer feels like doing.
Serguei
- Original Message -
From: Mark Johnson [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Friday, September 30, 2005 3:22 AM
Subject: Re: [U2] Good Programming Practice Question
The one you don't understand what it is doing when you see it for the first
time.
- Original Message -
From: Mark Johnson [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Friday, September 30, 2005 3:55 AM
Subject: Re: [U2] Good Programming Practice Question.
Define
Sometimes, if a subroutine is only called during certain situations (thus,
not often) and the file used by the subroutine is not used by the main
program, opening the file within the subroutine that uses it makes sense to
me.
-
From: Mark Johnson
One thing that has been over-looked in this conversation is the notion of
'lowest common denominator programming'.
My software runs on all MV platforms. Therefore, whenever possible, I stick
with syntax that works on all platforms. When that is not possible, I
resort to calls and includes and
Fair enough.
Mark Johnson
- Original Message -
From: Serguei [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Friday, September 30, 2005 4:29 AM
Subject: Re: [U2] Good Programming Practice Question.
The one you don't understand what it is doing when you see
Sometimes, if a subroutine is only called during certain situations (thus,
not often) and the file used by the subroutine is not used by the main
program, opening the file within the subroutine that uses it makes sense
to
me.
One problem with that Susan - what happens if the file doesn't
and use a
precompiler to handle the differences)
Brian
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Susan Joslyn
Sent: 30 September 2005 13:17
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Good Programming Practice Question.
One
Serguei wrote:
The one you don't understand what it is doing when you see it for the first
time.
I like that ..
but
it might instead be the algorithm that is hard
to understand if you're not familiar with it.
E.g the first time you see a parser 's central loop
you're not likely to grasp
And your SOX auditors haven't had a cow over that practice? Ours about
died from apoplexy when they saw all the archive stuff in our production
file. The only thing allowed in the production file are the programs
currently in production. We were forced to create a non-compilable
archive
FOR X = 1 TO PROMPT.CNT
*some code here*
*Back up one prompt*
X = X - 1 - (X # 1)
NEXT X
Gordon J. Glorfield
Sr. Applications Developer
MAMSI (A UnitedHealth Company)
301-360-8839
[EMAIL PROTECTED] wrote on 09/29/2005 10:55:26 PM:
Define tricky looking code.
Thanks.
The first programming book I read called this the:
Shirley Temple Principle - i.e.. Don't' get too cute.
It provided an example of a multi-line If-Then-Else construct
compressed into one line. Strangely enough it kind of looked like some
f-correlatives I've seen.
Colin Alfke
Calgary, Canada
it more difficult to
understand the code without giving anything in return.
- Original Message -
From: Mark Johnson [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Tuesday, September 27, 2005 10:46 PM
Subject: Re: [U2] Good Programming Practice Question.
Another good
I agree. Subroutines should be of a reasonable size for the task to be
performed, but to limit by lines is really unnecessary. In fact it can
lead to a over-use of subroutines (yes there is such a thing) that creates
very fragmented code. I was guilty of this in a sizable utility and it
became
Original Message
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Richard Taylor
Sent: Friday, September 30, 2005 7:53 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
I would add a few:
1) no multi-command lines (i.e
@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
BUTYou have to be careful that what is on the line doesn't have an
ELSE clause of it's own which is optional..(ie. WRITE).
IF (COND) THEN WRITE SOMETHING ON F.FILE,ID ELSE RELEASE F.FILE,ID
which needs to be
IF (CONT
@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
I don't mind if-then-else on one line ... as long as it fits on one
*screen* line. :) IF SOME.FLAG THEN GOSUB DO.SOMETHING ELSE GOSUB
DO.SOMETHING.ELSE
And I'm completely opposite, preferring a full block IF statement all
: Friday, September 30, 2005 12:23 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
C'mon! How difficult *is* it with your editor to convert it to block
format when either clause becomes multi-line?!?
-Keith
Original Message
From: [EMAIL
Exception to no multi-command lines.
TOT(1,1)=0; TOT(1,2)=0; TOT(1,3)=0; TOT(1,4)=0; * Resets array for this loop
And as far as no MATREADS/WRITES. You can always INCLUDE the DIM
statements. Which can also include the equates for standardized
variable names for each attribute. And yeah,
: Friday, September 30, 2005 8:18 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
Susan,
You make a good point, but the problem with that approach is that it stifles
innovation and learning - though not in your case, of course :-)
I have known
: Colin Jennings [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Friday, September 30, 2005 9:00 AM
Subject: Re: [U2] Good Programming Practice Question.
Sometimes, if a subroutine is only called during certain situations
(thus,
not often) and the file used by the subroutine
Is compression bad? One could debate the intracicies of when to use
multi-line IF-THEN-ELSE and when to keep it as one line.
My 1 cent
- Original Message -
From: [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Friday, September 30, 2005 9:38 AM
Subject: RE: [U2] Good Programming
on flame proof suit.
Louis
- Original Message -
From: Mark Johnson [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Friday, September 30, 2005 8:38 PM
Subject: Re: [U2] Good Programming Practice Question.
: Kevin:
: It happened already. One poster said that subs
I understand the concept of tagging changed lines but this seems to suggest
that deletions are commented out instead of removed. After four or five
changes you get confused about what is executing and what isn't. I am a
strong proponent of removing deleted lines of code.
---
u2-users
Thanks a lot for all the input on this subject.
Cheers
Mohamed
__
Yahoo! for Good
Donate to the Hurricane Katrina relief effort.
http://store.yahoo.com/redcross-donate3/
---
u2-users mailing list
please.
I like testing subs at TCL and the external OPEN's get in the way.
Mark Johnson
- Original Message -
From: [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Wednesday, September 28, 2005 8:43 AM
Subject: RE: [U2] Good Programming Practice Question.
I may have missed
This thread, while starting on noble grounds of 'good' programming
practices, will eventually turn into a pissing contest of implied standards.
Will?
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
, September 28, 2005 11:55 AM
Subject: RE: [U2] Good Programming Practice Question.
I've got to disagree with this one. This is the job of your source code
control system. I've seen applications which were commented in this manner
over a number of years and they are almost unreadable due
Message -
From: Allen E. Elwood [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Wednesday, September 28, 2005 12:28 PM
Subject: RE: [U2] Good Programming Practice Question.
I'll second that motion. If you *really* want source control, get serious
about it and save all previous
] Good Programming Practice Question.
I prefer alphanumeric labels for subroutines. The label should give some
clue as to the function of the subroutine. The subroutines should be in
frequency of use order with the most commonly used closer to the top of
the program. Subroutines
Define tricky looking code.
Thanks.
- Original Message -
From: Serguei Poliakov [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Thursday, September 29, 2005 5:09 AM
Subject: Re: [U2] Good Programming Practice Question.
I thinks the better to say - if the code looks
: Wednesday, September 28, 2005 4:22 PM
Subject: RE: [U2] Good Programming Practice Question.
Original Message
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Gordon J Glorfield
Sent: Wednesday, September 28, 2005 10:34 AM
To: u2-users@listserver.u2ug.org
Cc: [EMAIL
]
To: u2-users@listserver.u2ug.org
Sent: Thursday, September 29, 2005 5:27 AM
Subject: Re: [U2] Good Programming Practice Question.
Why do you need to create an extra variable (LAST)? It only make sense if
the number of elements in ARRAY is really big. If you expect it to have 1
to
10
This thread, while starting on noble grounds of 'good' programming
practices, will eventually turn into a pissing contest of implied
standards.
I normally ignore you, but this one has me interested. Why must this
otherwise educational topic be degraded into implication?
-K
---
u2-users
my general distain for her approach to things,
I can gleen something useful for my future.
My 1 cent.
- Original Message -
From: Fawaz Ashraff [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Thursday, September 29, 2005 4:33 PM
Subject: RE: [U2] Good Programming Practice Question
[EMAIL PROTECTED] wrote:
We also use xnn.meaningful.name type labels. One advantage is that our
editor can recognise a label and putting the cursor on a line that
includes a GOSUB and pressing one function key will move the cursor
directly to the correct paragraph.
One thing I've never
I may have missed someone else mentioning this, don't open files in an
external subroutine that is called from within a loop. Yeah, yeah, I know
you can set up a common, but isn't it cleaner to open the file in the main
routine?
Bruce M Neylon
Health Care Management Group
---
u2-users
Two items I have thought of.
1. In addition to putting a modification tag at the top of the code with
who/date/what, we also will assign a job number to the mod in addition to a No
for the mod. Such as mod 01. Then throughout the code where the changes are
made we put a tag such as *01 start
@listserver.u2ug.org
cc
Subject
RE: [U2] Good Programming Practice Question.
Two items I have thought of.
1. In addition to putting a modification tag at the top of the code with
who/date/what, we also will assign a job number to the mod in addition to
a No for the mod. Such as mod 01
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Marilyn Hilb
Sent: Wednesday, September 28, 2005 7:48 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
Two items I have thought of.
1. In addition to putting a modification tag
:[EMAIL PROTECTED] Behalf Of Womack, Adrian
Sent: Tuesday, September 27, 2005 18:06
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
We also use xnn.meaningful.name type labels. One advantage is that our
editor can recognise a label and putting
Of Marilyn Hilb
Sent: Wednesday, September 28, 2005 8:48 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
Two items I have thought of.
1. In addition to putting a modification tag at the top of the code with
who/date/what, we also will assign
] Good Programming Practice Question.
Regarding the origin and revisions to software, DataFlo
programmers pretty much have followed the policy where you
try to flag all revisions in the software using the following
convention:
* Baseline changes use just a rev#, for example rev 01
changes
I came up with a program under 100 lines.
- Original Message -
From: Jeff Schasny [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Wednesday, September 28, 2005 10:55 AM
Subject: RE: [U2] Good Programming Practice Question.
I've got to disagree with this one
One beauty of using a source control system like RCS or SCCS is that you
do not need to maintain the mods in the source, the current running
version of the source looks clean, but you can also view or print out
the incremental differences.
When I first introduced using RCS at one shop I got
I prefer alphanumeric labels for subroutines. The label should give some
clue as to the function of the subroutine. The subroutines should be in
frequency of use order with the most commonly used closer to the top of
the program. Subroutines that are used once in a program (file opens,
Strange, while we are discussing this Gus has already set up a web seminar
on the subject:
http://www.intl-spectrum.com/learn%20more%20page.3A.htm
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Original Message
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Gordon J Glorfield
Sent: Wednesday, September 28, 2005 10:34 AM
To: u2-users@listserver.u2ug.org
Cc: [EMAIL PROTECTED]; u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question
:22
To: u2-users@listserver.u2ug.org
Cc: [EMAIL PROTECTED]
Subject: RE: [U2] Good Programming Practice Question.
Original Message
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Gordon J Glorfield
Sent: Wednesday, September 28, 2005 10:34 AM
To: u2-users
the approach to keep the stamp and story at the top, but remove the
tags after a while.
-Original Message-
[mailto:[EMAIL PROTECTED] Behalf Of Marilyn Hilb
Sent: Wednesday, September 28, 2005 8:48 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question
I've been teaching UniBasic for over 10 years and here are some of the
methods I teach:
* Subroutines should only have one job.
* Subroutines should be short. (less than 10 lines)
* Subroutines should have one entrance and one exit.
* Use meaningful variable names and subroutine names.
* Be
I like these and would add another one - Add comments to tricky-looking
code!
-Dianne
David A. Green wrote:
I've been teaching UniBasic for over 10 years and here are some of the
methods I teach:
* Subroutines should only have one job.
* Subroutines should be short. (less than 10 lines)
*
*
George
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Dianne Ackerman
Sent: Tuesday, September 27, 2005 2:57 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Good Programming Practice Question.
I like these and would add
: [U2] Good Programming Practice Question.
Also, how about a change log at the top of the program
that lists, who, when and what/why a change was made.
add to that a short description as to what the function
of the program is for.
* this program does .
*
*
* date who changes made
Yes good one.
The more readable your code the easier to DEBUG and to reuse.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dianne Ackerman
Sent: Tuesday, September 27, 2005 11:57 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Good Programming
On 9/27/05, Dianne Ackerman [EMAIL PROTECTED] wrote:
I like these and would add another one - Add comments to tricky-looking
code!
-Dianne
And DON'T add comments to the mundane routine stuff!!
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit
of the program is near unforgiveable.
-K
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Allen E.
Elwood
Sent: Tuesday, September 27, 2005 12:40 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
My addition
] Behalf
Of George Gallen
Sent: Tuesday, September 27, 2005 12:12
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice
Question.
Also, how about a change log at the top of the
program
that lists, who, when and what/why a change was
made.
add
In addition to using subroutines, when developing with UniVerse and SB+
I often have one application handle many, if not all of the screen and
report processing. This helps keep things in one place. For this I use
the ON GOSUB construct of the BASIC language. It's worth noting
depending on its
-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
And here's where the conflict begins. When looking through a big
program, I much prefer numeric labels in order with comments vs.
alphanumeric labels. With numeric labels in order you find 1800 and
if you're
Try not to use dim arrays to hold file variables. difficult to diag.
Keep label and variable names to 14 chars and under for universe's xrefer
Avoid ever 'falling' into a label
Never branch around stuff
Sometimes its nice to comment CASE statements
CASE LEN(ID) LE 5 ;* its a phone number
..
On
] On Behalf Of Kevin King
Sent: Tuesday, September 27, 2005 1:04 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
And here's where the conflict begins. When looking through a big
program, I much prefer numeric labels in order with comments vs
: Tuesday, September 27, 2005 12:40 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
My addition to this would be to use alphanumeric labels, and to *have*
a main calling section. A main calling section that looks like:
GOSUB OPEN.AND.INIT
GOSUB
Sent: Tuesday, September 27, 2005 12:12
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
Also, how about a change log at the top of the program
that lists, who, when and what/why a change was made.
add to that a short description
]
To: u2-users@listserver.u2ug.org
Sent: Tuesday, September 27, 2005 2:40 PM
Subject: RE: [U2] Good Programming Practice Question.
My addition to this would be to use alphanumeric labels, and to *have* a
main calling section. A main calling section that looks like:
GOSUB OPEN.AND.INIT
GOSUB
] On Behalf Of Kevin King
Sent: 27 September 2005 21:04
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
And here's where the conflict begins. When looking through a
big program, I much prefer numeric labels in order with comments vs
alphabetize the labels? You mean sort?? :-)
-K
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill_H
Sent: Tuesday, September 27, 2005 1:35 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
Kevin
-
From: Kevin King [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Tuesday, September 27, 2005 3:03 PM
Subject: RE: [U2] Good Programming Practice Question.
And here's where the conflict begins. When looking through a big
program, I much prefer numeric labels in order with comments
I prefer alphanumeric labels for subroutines. The label should give some
clue as to the function of the subroutine. The subroutines should be in
frequency of use order with the most commonly used closer to the top of
the program. Subroutines that are used once in a program (file opens,
What about lock management?
1. Lock all records that are going to be updated ... even if the update
is really a delete
2. Release your locks promptly (either with a RELEASE, WRITE or DELETE
statement) - don't let the program termination be the time when record
locks are released
3. Use the LOCKED
-Keith
Original Message
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill_H
Sent: Tuesday, September 27, 2005 1:35 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
Kevin:
Not if you alphabetize the labels; then it works
PM
Subject: RE: [U2] Good Programming Practice Question.
I most heartily agree! Numbers in the labels don't elucidate; they merely
increase the length. And I'm pretty sure I know that U comes somewhere
after S. :)
My $0.02 (on issues ancillary to the code itself) ...
- make your BP
associated attributes.
My 1 cent.
- Original Message -
From: Keith W. Roberts [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Tuesday, September 27, 2005 5:14 PM
Subject: RE: [U2] Good Programming Practice Question.
I most heartily agree! Numbers in the labels don't elucidate
TO F.CUSTOMER ELSE STOP ;* RWCD
- Original Message -
From: Keith W. Roberts [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Tuesday, September 27, 2005 5:14 PM
Subject: RE: [U2] Good Programming Practice Question.
I most heartily agree! Numbers in the labels don't elucidate
@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
alphabetize the labels? You mean sort?? :-)
-K
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill_H
Sent: Tuesday, September 27, 2005 1:35 PM
To: u2-users
I recommend that everyone buy/borrow a copy of Code Complete by Steve
McConnell. It has several sections dedicated to good coding practices.
Readability is key, since we read programs hundreds of times more than we
write them. The book offers lots of strategies to improve readability, like
Mark Johnson
P.S. I would also love to see an analyzer program that identifies whether
OPENed files READ, WRITE, CLEAR and/or DELETE. It could be a comment at the
end of the OPEN statement. Often times I FIND a BP file for CUSTOMER and
WRITE but they're not necessarily attached.
I like having a
, September 27, 2005 3:48 PM
Subject: RE: [U2] Good Programming Practice Question.
Kevin,
I disagree, for a simple reason:
I use alpha labels that make sense and then place them in the code in
alphabetical order.
Problem solved grin.
Just a few off the top of my head (it's late here):
1
COL.FMT
RETURN
!
END
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Woodward
Sent: Tuesday, September 27, 2005 1:30 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
I agree with Kevin, specifically
Original Message
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Leach
Sent: Tuesday, September 27, 2005 1:49 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
Kevin,
I disagree, for a simple reason:
I use alpha
RETURN with a comment..that is an excellent suggestion.
Nancy
- Original Message -
From: Mark Johnson [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Tuesday, September 27, 2005 2:51 PM
Subject: Re: [U2] Good Programming Practice Question.
Another
@listserver.u2ug.org
Subject: [ ] - RE: [U2] Good Programming Practice Question. -
Found word(s) list error in the Text body
Bob,
10 lines is a good rule to live by. There are some exceptions like
the
Initialization routine or large CASE structures that have many
options
, 2005 2:17 PM
To: u2-users@listserver.u2ug.org
Cc: [EMAIL PROTECTED]; u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
I prefer alphanumeric labels for subroutines. The label should give
some clue as to the function of the subroutine. The subroutines
should
RETURN with a comment..that is an excellent suggestion.
I'd argue that any END statement that's more than a handful (8-10) lines
from the opening IF (or whatever) statement should have a comment.
Here's an example (that's not long enough to satisfy my 'handful' argument
above):
We also use xnn.meaningful.name type labels. One advantage is that our
editor can recognise a label and putting the cursor on a line that
includes a GOSUB and pressing one function key will move the cursor
directly to the correct paragraph.
One thing I've never agreed with (except in COBOL) is
This is where the FIND command becomes handy
From: [EMAIL PROTECTED] on behalf of Kevin King
Sent: Tue 9/27/2005 4:03 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
And here's where the conflict begins
Allen:
I know we've seen the same crappy code LOL
From: [EMAIL PROTECTED] on behalf of Allen E. Elwood
Sent: Tue 9/27/2005 4:27 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] Good Programming Practice Question.
AhI always put my
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, 28 September 2005 7:11 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Good Programming Practice Question.
RETURN with a comment..that is an excellent suggestion.
I'd argue
90 matches
Mail list logo
