In message
[EMAIL PROTECTED], Norman
Morgan [EMAIL PROTECTED] writes
I'm with you on the CAPS issue. I do find the code in caps easier to
read. Perhaps I'm just used to it from the first 20 years of my career
spent writing COBOL. I think the layout of the code and choice of
variable and
On 14/03/07, MAJ Programming [EMAIL PROTECTED] wrote:
How does using upper case make a programmer primitive?
Considering that beaucoups of prior source code is in pure upper case, it
would be hard to cost justify changing the case for its own sake.
Accuterm's WED program editor allows you
On 14/03/07, MAJ Programming [EMAIL PROTECTED] wrote:
I'm gonna throw my 4 cents in to hopefully stop this excessive coding.
or this doozy of a mess
OPEN FILE1 TO F.FILE1 THEN
OPEN FILE2 TO F.FILE2 THEN
OPEN FILE3 TO F.FILE3 THEN
500 LINES OF PROCESSING AS
Mark
I WAS WAITING FOR YOU TO RESPOND THERE!
SO YOU PREFER CODE THAT SHOUTS BACK AT YOU?
THERE ARE GOOD REASONS WHY THE REST OF THE WORLD HAS SWITCHED TO MIXED CASE
CODING - IT IS GENUINELY QUICKER TO SCAN AND READ. FORTUNATELY I'VE ONLY BEEN
WITH MULTIVALUE FOR TWENTY YEARS SO I WAS ABLE TO
:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: 14 March 2007 09:16
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Error in report generation.
Mark
I WAS WAITING FOR YOU TO RESPOND THERE!
SO YOU PREFER CODE THAT SHOUTS BACK AT YOU?
THERE ARE GOOD REASONS WHY THE REST OF THE WORLD HAS
with a program, then WED is great.
I promote WED whenever I can. The support is beyond 100% great.
Mark Johnson
- Original Message -
From: Symeon Breen [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Wednesday, March 14, 2007 4:05 AM
Subject: Re: [U2] Error in report generation
:16
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Error in report generation.
Mark
I WAS WAITING FOR YOU TO RESPOND THERE!
SO YOU PREFER CODE THAT SHOUTS BACK AT YOU?
THERE ARE GOOD REASONS WHY THE REST OF THE WORLD HAS SWITCHED TO MIXED
CASE CODING - IT IS GENUINELY QUICKER TO SCAN
]
To: u2-users@listserver.u2ug.org
Sent: Wednesday, March 14, 2007 4:10 AM
Subject: Re: [U2] Error in report generation.
On 14/03/07, MAJ Programming [EMAIL PROTECTED] wrote:
I'm gonna throw my 4 cents in to hopefully stop this excessive coding.
or this doozy of a mess
OPEN FILE1
scenario in favor or using
Loop While Readnext Id From MYLIST Do
My 4 cents
Mark Johnson
- Original Message -
From: [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Wednesday, March 14, 2007 4:16 AM
Subject: Re: [U2] Error in report generation.
Mark
I WAS WAITING FOR YOU
I must be backwards because I actually find the second one easier to
read and cleaner. And faster to type! Of course, I guess I'm one of
the old-timers, having been in multi-value for 25 years now.
-Dianne
[EMAIL PROTECTED] wrote:
Mark
I WAS WAITING FOR YOU TO RESPOND THERE!
SO YOU PREFER
: Spam:Re: [U2] Error in report generation.
Mark
I WAS WAITING FOR YOU TO RESPOND THERE!
SO YOU PREFER CODE THAT SHOUTS BACK AT YOU?
THERE ARE GOOD REASONS WHY THE REST OF THE WORLD HAS SWITCHED TO MIXED
CASE CODING - IT IS GENUINELY QUICKER TO SCAN AND READ. FORTUNATELY I'VE
ONLY BEEN
All,
For my two cents, I *rarely* code in mixed case when I'm in an MV
environment. I use upper/lower in comments to make them stand out - a
trick I adopted from my friend Scott Lustig. Having said that, I
believe that the future is, as Brian suggests, in making our code look
more like
snip
... all uppercase is hard to read. Here's why.
Humans don't read by assembling the letters into a word, we read by
recognizing the overall image of the printed word and converting it into
its meaning. Thus, the incredibly random nature of regular conversation
supports this theory. We're used
] On Behalf Of
Dianne Ackerman
Sent: Wednesday, March 14, 2007 8:27 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Error in report generation.
I must be backwards because I actually find the second one
easier to read and cleaner. And faster to type! Of course,
I guess I'm one
@listserver.u2ug.org
Subject: Re: [U2] Error in report generation.
I must be backwards because I actually find the second one easier to read
and cleaner. And faster to type! Of course, I guess I'm one of the
old-timers, having been in multi-value for 25 years now.
-Dianne
[EMAIL PROTECTED] wrote
Bill: I don't grasp which side of this fence you're on with this post.
- Original Message -
From: Bill H [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Wednesday, March 14, 2007 3:45 PM
Subject: RE: [U2] Error in report generation.
An interesting test would be for those who
Hi
I tried to generate a report by writing a small program. But I got an error
as below.
ERROR:
RUN TEST.BP MAIN
MAIN
45 record(s) selected to SELECT list #0.
Program SUB: Line 3, Variable REC previously undefined. Empty string
used.
Program SUB: Line 3, Printer name UVDEFAULT is not
@listserver.u2ug.org
Subject: [U2] Error in report generation.
Hi
I tried to generate a report by writing a small program. But I got an error
as below.
ERROR:
RUN TEST.BP MAIN
MAIN
45 record(s) selected to SELECT list #0.
Program SUB: Line 3, Variable REC previously undefined. Empty string
Perhaps a little explanation is in order here.
There are no global variables in u2.
Thus the need to pass the variables to the subroutine.
If you have truly global variables - used in many subroutines - you could
put them in a common block.
( add a line
COMMON /name/ REC, VAR
in every
Hi Sanjeebkumar,
you have to pass variables from the calling program to the subroutine,
otherwise they will not be defined in the subroutine.
Line 12 in your calling program (MAIN) should therefore look like this:
CALL SUB(REC)
and line 1 in your subroutine (SUB) should be
SUBROUTINE SUB(REC)
Hi
You need to pass REC as a parameter to the subroutine see below:
-- mats
Sanjeebkumar Sarangi skrev:
Hi
I tried to generate a report by writing a small program. But I got an error
as below.
ERROR:
RUN TEST.BP MAIN
MAIN
45 record(s) selected to SELECT list #0.
Program
Charles Barouch wrote:
Sanjeeb,
There are several problems with this and I strongly suggest you get
some training. [AD] My company, Key Ally, does training[/AD].
However, in brief: Variables are only global within a program. Once
you CALL SUB, you are in a new program and all variables
This wont work either:
L#16:REC1
Try this:
REC1 L#16
Sanjeebkumar Sarangi wrote:
Hi
I tried to generate a report by writing a small program. But I got an error
as below.
ERROR:
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit
And the pretty version:
Brian
* define some field locations. Normally these would be placed in
* a separate include file and shared.
EQU INVENTORY.CODE To 1
EQU INVENTORY.DESCRIPTION To 2
EQU INVENTORY.TYPE To 3
* only primitive programmers still use upper case!
Crt Main
Ct = 0
Open
Is this going to become a pissing-contest?
[EMAIL PROTECTED] schrieb:
And the pretty version:
Brian
* define some field locations. Normally these would be placed in
* a separate include file and shared.
EQU INVENTORY.CODE To 1
EQU INVENTORY.DESCRIPTION To 2
EQU INVENTORY.TYPE To 3
* only
No :)
But he is just learning BASIC, so he might as well start with some good
conventions - like using EQUATEs for field numbers.
Brian
Is this going to become a pissing-contest?
[EMAIL PROTECTED] schrieb:
And the pretty version:
Brian
---
u2-users mailing list
Mecki FC6rthmann wrote:
Is this going to become a pissing-contest?
snip
Actually it's a fairly interesting thread, presenting a couple options
for the original poster, along with various styles of coding for him/her
to look at and think about. Not a bad thing.
--
Allen Egerton
aegerton
Instead - why not use the Retrieve language from the command line
without bothering with a basic program? Type the following at the
command line will give you the result your program is trying to acheive:
SORT INVENTORY BY ITEM_CODE ITEM_CODE CONV T16 DESCRIPTION CONV T16
TYPE CONV T16
-
From: [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Tuesday, March 13, 2007 11:00 AM
Subject: Re: [U2] Error in report generation.
And the pretty version:
Brian
* define some field locations. Normally these would be placed in
* a separate include file and shared.
EQU
] Error in report generation.
Hi
I tried to generate a report by writing a small program. But I got an
error
as below.
ERROR:
RUN TEST.BP MAIN
MAIN
45 record(s) selected to SELECT list #0.
Program SUB: Line 3, Variable REC previously undefined. Empty string
used.
Program SUB: Line 3
30 matches
Mail list logo
