Sent: 25 July 2007 18:55
To: 'u2-users@listserver.u2ug.org'
Subject: RE: [U2] : Cleaner Case Statement
Martin:
Thanks very much indeed.
--Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Martin Phillips
Sent: Wednesday, July 25, 2007 12:38 PM
To: u2
ON is bad because it is in violation of the KISS principle. (Keep It So
Simple)
--Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Perry Taylor
Sent: Wednesday, July 25, 2007 2:53 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [u2] : Cleaner
Hold the phone... That's a valid syntax? On what platform?
On 7/25/07, Martin Phillips [EMAIL PROTECTED] wrote:
ON is bad because it is in violation of the KISS principle. (Keep It
So
Simple)
You have to be kidding!
Consider a simple menu option processor...
INPUT OPTION
IF OPTION
Phillips
Sent: Wednesday, July 25, 2007 4:28 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Cleaner Case Statement
ON is bad because it is in violation of the KISS principle. (Keep It
So
Simple)
You have to be kidding!
Consider a simple menu option processor...
INPUT OPTION
IF OPTION MATCHES
To answer the question... that was not the original question.
The original question is just under I would like something like...
Martin Philips indicated that what I want cannot be done right now with
UniBasic.
--Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Personally I like the match or index syntax.
case ans match 'b':@vm:2 gosub checkb
case index('b2',quote(ans),1) gosub checkb
I also continue to feel there is a very good case for subroutine indirection
which would give:
sub = 'check':ans
gosub @sub
Martin:
Thanks very much indeed.
--Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Martin Phillips
Sent: Wednesday, July 25, 2007 12:38 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] [u2] : Cleaner Case Statement
Hi Bill,
Unlike languages
