Hi Will,
As I said, I don't use it myself, but a reason one might use
it is that one can easily cut and paste (or include) logic.
For example:
---
LOCKED
put
some
generic
logic
here
END
---
regards, Keith
WJohnson wrote:
Why the extra lines? Why not just
IF
Why the extra lines? Why not just
IF A = "TEST" THEN
gosub do.something
END ELSE
gosub do.something.else
END
<<>>
-Original Message-
From: Keith Johnson [DATACOM]
To: 'u2-users@listserver.u2ug.org'
Sent: Mon, Apr 23, 2012 5:44 pm
Subje
I prefer the layout of
IF A = "TEST"
THEN GOSUB DO.SOMETHING ;* Say why
ELSE GOSUB DO.SOMETHING.ELSE ;* The reason
However, here is a form that's rarely used, but does work.
IF A = "TEST"
THEN ;* say why in a long-winded manner
GOSUB DO.SOMETHING
END
012 8:50 a.m.
> To: u2-users@listserver.u2ug.org
> Subject: Re: [U2] Case Statement with only two cases... or for that matter...
> one case
>
> Well,
>
> I prefer:
>
> IF A = "TEST" THEN
> GOSUB DO.SOMETHING ;* Say why
> END
r.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of dennis bartlett
Sent: Saturday, April 21, 2012 4:06 PM
To: U2 Users List
Subject: Re: [U2] Case Statement with only two cases... or for that
matter... one case
@Mecki.. What is your editor of choice, ie can you get it to indent 1 s
@Mecki.. What is your editor of choice, ie can you get it to indent 1
space? I've always been a standard FORMAT in ED fella, but the site I've
just joined doesn't want that, code must start right up against the edge, &
have 2 space indenting.. So hard to not instinctively FORMAT, & equally
hard to
Well,
I prefer:
IF A = "TEST" THEN
GOSUB DO.SOMETHING ;* Say why
END ELSE
GOSUB DO.SOMETHING.ELSE ;* The reason
END
IMO much more readable - because you see immediately that is is a
conditional branching.
It is also easier maintainable if you want to ad
Rather than:
BEGIN CASE
CASE A = "TEST"; GOSUB DO.SOMETHING
CASE 1; GOSUB DO.SOMETHING.ELSE
END CASE
or
IF A = "TEST" THEN GOSUB DO.SOMETHING ELSE GOSUB DO.SOMETHING.ELSE
I prefer:
IF A = "TEST" THEN GOSUB DO.SOMETHING ;* Say why
ELSE GOSUB DO.SOMETHING
t way,
but it does make a kind of sense.
-Original Message-
From: Charles Stevenson
To: U2 Users List
Sent: Fri, Apr 20, 2012 6:28 am
Subject: Re: [U2] Case Statement with only two cases
A respectful correction, Brian.
On 4/20/2012 4:50 AM, Brian Leach wrote:
it's all the
You just want all the jobs to yourself :)
-Original Message-
From: Symeon Breen
To: 'U2 Users List'
Sent: Fri, Apr 20, 2012 1:45 am
Subject: Re: [U2] Case Statement with only two cases... or for that matter...
one case
Both read exactly the same to me - the case probab
14:28
To: U2 Users List
Subject: Re: [U2] Case Statement with only two cases
A respectful correction, Brian.
On 4/20/2012 4:50 AM, Brian Leach wrote:
> it's all the same to the compiler.
> -Original Message-
> BEGIN CASE
>CASE A = "TEST"; GOSUB D
g, Pure System? In many ways, a 180 degree turn: everything is back in
one rack: cpu's, storage, networking...
> Date: Fri, 20 Apr 2012 08:27:48 -0500
> From: stevenson.c...@gmail.com
> To: u2-users@listserver.u2ug.org
> Subject: Re: [U2] Case Statement with only two cases
>
&
theoretically optimize. cds"
Amen!
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Charles Stevenson
Sent: Friday, April 20, 2012 7:28 AM
To: U2 Users List
Subject: Re: [U2] Case Statement with only two
A respectful correction, Brian.
On 4/20/2012 4:50 AM, Brian Leach wrote:
it's all the same to the compiler.
-Original Message-
BEGIN CASE
CASE A = "TEST"; GOSUB DO.SOMETHING
CASE 1; GOSUB DO.SOMETHING.ELSE
END CASE
versus this
IF A = "TEST" THEN GOSUB DO.SOMETHI
pril 2012 09:45
To: 'U2 Users List'
Subject: Re: [U2] Case Statement with only two cases
Or perhaps there were more cases in there, and over the years they have been
deleted. The last programmer to have done a deletion probably should have
turned it into an if - but I don'
Breen
Sent: 20 April 2012 09:45
To: 'U2 Users List'
Subject: Re: [U2] Case Statement with only two cases
Or perhaps there were more cases in there, and over the years they have been
deleted. The last programmer to have done a deletion probably should have
turned it into an if - but I don&
econd ;)
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Dave Laansma
Sent: 19 April 2012 20:57
To: U2 Users List
Subject: Re: [U2] Case Statement with only two cases
Logically they are clearly the same. It just depends on
...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Brutzman
Sent: 19 April 2012 22:42
To: U2 Users List
Subject: Re: [U2] Case Statement with only two cases... or for that
matter... one case
The initial example was close to a good start... something like...
If
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson
Sent: Thursday, April 19, 2012 7:50 PM
Subject: Re: [U2] Case Statement
Replacing one line with four lines...
___
U2
You replace one line with four lines
I'm an atheist regarding the belief in code bloat
-Original Message-
From: Bill Brutzman
To: U2 Users List
Sent: Thu, Apr 19, 2012 4:48 pm
Subject: Re: [U2] Case Statement with only two cases... or for that matter...
one case
The in
I don't understand why you'd want this
<>
-Original Message-
From: dennis bartlett
To: U2 Users List
Sent: Thu, Apr 19, 2012 4:45 pm
Subject: Re: [U2] Case Statement with only two cases... or for that matter...
one case
Well, I wrote a proggie to process sourc
Well, I wrote a proggie to process source code and break long IF/THEN/ELSE
into
IF ... THEN
END ELSE
END
and also
SEL.VERB = 'SELECT FILE WITH J=1 AND K=2 AND L=3 BY ABC BY DEF BREAK-ON XYZ
TO
SEL.VERB = ''
SEL.VERB := "SELECT FILE"
SEL.VERB := " WITH J=1 AND"
SEL.VERB := " K=2 AND"
SEL.VERB :
sday, April 19, 2012 2:42 PM
To: U2 Users List
Subject: Re: [U2] Case Statement with only two cases... or for that
matter... one case
The initial example was close to a good start... something like...
If XX then gosub YY else gosub ZZ
Replaced by
Begin case
o:u2-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson
Sent: Thursday, April 19, 2012 5:33 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Case Statement with only two cases... or for that matter...
one case
Give an example of, with what you would replace t
-users@listserver.u2ug.org
Subject: Re: [U2] Case Statement with only two cases... or for that matter...
one case
Give an example of, with what you would replace the If Then Else
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http
Give an example of, with what you would replace the If Then Else
-Original Message-
From: Bill Brutzman
To: U2 Users List
Sent: Thu, Apr 19, 2012 2:26 pm
Subject: Re: [U2] Case Statement with only two cases... or for that matter...
one case
1.Problematic... [a] I run into sloppy
-users-boun...@listserver.u2ug.org] On Behalf Of Wjhonson
Sent: Thursday, April 19, 2012 4:57 PM
Subject: Re: [U2] Case Statement with only two cases... or for that matter...
one case
Explain more what you mean by saying the if is problematic and obsolete
Explain more what you mean by saying the if is problematic and obsolete ?
-Original Message-
From: Bill Brutzman
To: U2 Users List
Sent: Thu, Apr 19, 2012 1:35 pm
Subject: Re: [U2] Case Statement with only two cases... or for that matter...
one case
The case statement has a huge
The case statement has a huge advantage in what really matters... human
readability... that is the point.
>From readability follows... reliability, maintainability, and testability...
>better, cleaner, safer software.
An irony is that while the "if" statement... is the cornerstone of all
comp
The case statement can be faster if you put the condition with the most
occurrences first. As soon as the 'true' condition is met, the program exits
the case statement. The if-then-else construct took longer to evaluate. When
processors were slow, there were gains to be had.
Richard Sammartin
As others have mentioned, they're functionally equivalent. The CASE
construct leaves it open for additional options, although I hardly think
that's a reason to use it, since it's simple enough to convert an
if/then/else to a CASE if need be.
>From a stylistic standpoint, I dislike if/then/else al
t: Re: [U2] Case Statement with only two cases
Makes FUTURE maintenance MUCH easier if you want to add 1 or 2 or 5 more
cases
On Thu, Apr 19, 2012 at 2:52 PM, Wjhonson wrote:
>
> Is there a point in code like this
>
> BEGIN CASE
> CASE A = "TEST"; GOSUB
hat
it started with multiple cases, and was eventually whittled down to two.
Drew
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Colwell, Kim
Sent: Thursday, April 19, 2012 3:56 PM
To: U2 Users List
Subject: Re: [U2]
Logically they are clearly the same. It just depends on what the
programmer had in mind for the future of 'A'.
Sincerely,
David Laansma
IT Manager
Hubbard Supply Co.
Direct: 810-342-7143
Office: 810-234-8681
Fax: 810-234-6142
www.hubbardsupply.com
"Delivering Products, Services and Innovative Solu
Sometimes I build a case statement like this because I figure I'll grow
into it by the time I'm done doing what I'm trying to do. :-)
Bill
- Original Message -
*From:* wjhon...@aol.com
*To:* u2-users@listserver.u2
Makes FUTURE maintenance MUCH easier if you want to add 1 or 2 or 5 more
cases
On Thu, Apr 19, 2012 at 2:52 PM, Wjhonson wrote:
>
> Is there a point in code like this
>
> BEGIN CASE
> CASE A = "TEST"; GOSUB DO.SOMETHING
> CASE 1; GOSUB DO.SOMETHING.ELSE
> END CASE
>
> versus this
>
> IF
36 matches
Mail list logo
