Original Message
Subject:Re: [U2] [UV] Select Question
Date: Mon, 25 Jul 2005 21:23:44 -0400
From: Moderator <[EMAIL PROTECTED]>
Reply-To: u2-users@listserver.u2ug.org
To: u2-users@listserver.u2ug.org
THREAD CLOSED.
---
u2-users mailing list
u2
If you really want to debate the issue, contact either Ian Sandler or
Harvey Rodstein. The syntax came from one of their books.
Personally, I'm looking into the future and seeing a "THREAD CLOSED"
message from the moderator.
Charlie Rubeor
Unix/Database Admin
The Wiremold Company
800.338.1315
In a message dated 7/25/2005 11:38:53 AM Pacific Daylight Time,
[EMAIL PROTECTED] writes:
> The distinction with using an EOF variable is that it is not referenced,
> until the next READNEXT. Each new variable that is read into memory will
> push the EOF variable further to the back. This de
THREAD CLOSED.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Is not 'muscle-memory' phrases what makes for being an effecient programmer.
I can knock off a 5 field file maintenance program in around 10 minutes
without even 'thinking'. No 4gl's or other magic programming need apply.
Just pure code.
my 1 cent
>
I certainly identify with muscle-memory phra
sage -
From: "Stewart Leicester" <[EMAIL PROTECTED]>
To:
Sent: Monday, July 25, 2005 6:12 PM
Subject: Re: [U2] [UV] Select Question
> > > I challenge whatever book made this contention.
> >>
> >
> >Knock yourself out. I think it's in "Pick
We're beating a dead horse. I offered this method around 200 posts or 10
days ago.
Mark Johnson
- Original Message -
From: <[EMAIL PROTECTED]>
To:
Sent: Monday, July 25, 2005 12:17 PM
Subject: RE: [U2] [UV] Select Question
> I can NAME THAT TUNE in *** 2 *** notes:
> I challenge whatever book made this contention.
Knock yourself out. I think it's in "Pick For Professionals: Advanced
Methods & Techniques." by Harvey Rodstein. All I was trying to do was
explain where the syntax ELSE ID = @AM originated from. We've already
spent more time discussing the
@listserver.u2ug.org
Subject: RE: [U2] [UV] Select Question
Did you try using DO:
LOOP WHILE READNEXT ID DO
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Allen E. Elwood
Sent: Monday, July 25, 2005 4:29 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [UV
> I challenge whatever book made this contention.
>
Knock yourself out. I think it's in "Pick For Professionals: Advanced
Methods & Techniques." by Harvey Rodstein. All I was trying to do was
explain where the syntax ELSE ID = @AM originated from. We've already
spent more time discussing the
Did you try using DO:
LOOP WHILE READNEXT ID DO
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Allen E. Elwood
Sent: Monday, July 25, 2005 4:29 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [UV] Select Question
I also work on a PICK system
rk nicely on Unidata though :)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of gerry-u2ug
Sent: Monday, July 25, 2005 13:03
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [UV] Select Question
loop while readnext ID
blah blah blah
repeat
-Origin
The more important problem is that the variables are all mapped into a
contiguous workspace that is referenced so continously that it's
highly unlikely it
would ever get paged from memory, while your process is running, except
perhaps on systems that were so woefully underbuilt that paging
B
loop while readnext ID
blah blah blah
repeat
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
[EMAIL PROTECTED]
Sent: Monday, July 25, 2005 12:18 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [UV] Select Question
I can NAME THAT TUNE in *** 2
> There are a few problems with this theory. @AM is only a typical
component
> of U2 systems and so would not, most likely, have been included in
> the Advanced
@AM might not have been available then, but EQUATE was. Most programs
written before @AM was available usually equated the delimit
In a message dated 7/25/2005 9:46:28 AM Pacific Daylight Time,
[EMAIL PROTECTED] writes:
> Just phrase it as "I do things in a way that is safe, based on long
> experience, and consistent." Suddenly, it sounds downright conservative.
I like that.
How about also this tact
1) Do it my way, a
In a message dated 7/25/2005 7:25:53 AM Pacific Daylight Time,
[EMAIL PROTECTED] writes:
> I started to use this syntax (ELSE ID = @AM) several years ago. It
> originated, I think, from the "Advanced Pick Programming" book, circa
> 1990. The theory went that if you used a separate variable,
Marilyn,
Just phrase it as "I do things in a way that is safe, based on long
experience, and consistent." Suddenly, it sounds downright conservative.
- Chuck "Talk Like a Radical, Think Like a Liberal, Act like a
Conservative" Barouch
Marilyn Hilb wrote:
Quote: "These days, I still u
I can NAME THAT TUNE in *** 2 *** notes:
LOOP WHILE READNEXT ID DO
blah blah blah
REPEAT
;)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Martin Phillips
Sent: Monday, July 25, 2005 10:59 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] [UV
Quote: "These days, I still use the syntax because I my fingers can type it
from memory, without my brain actually working."
I Love that statement. A non-programmer just wouldn't understand and would
likely cause fear in them .. especially the bosses.. to know this is part of a
programmers inne
> > > >> READNEXT ID FROM LIST ELSE ID = @AM
> > > >But why do you use an odd convention like ID = @AM ?
> >
> > because it would be impossible for ID to be an attribute mark via
> > readnext.
> > If you later test for ([EMAIL PROTECTED]) there's only one way that could
> > have
> > happened
[EMAIL PROTECTED] wrote on 07/22/2005 10:08:02 PM:
> > >> READNEXT ID FROM LIST ELSE ID = @AM
> > >But why do you use an odd convention like ID = @AM ?
>
> because it would be impossible for ID to be an attribute mark via
> readnext.
> If you later test for ([EMAIL PROTECTED]) there's only o
> >> READNEXT ID FROM LIST ELSE ID = @AM
> >But why do you use an odd convention like ID = @AM ?
because it would be impossible for ID to be an attribute mark via
readnext.
If you later test for ([EMAIL PROTECTED]) there's only one way that could have
happened.
I'll admit to occasionally doi
Cute!
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of gerry-u2ug
Sent: Friday, July 22, 2005 15:11
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [UV] Select Question
LOOP while READNEXT ID
GOSUB DO.STUFF
REPEAT
-Original Message-
From
LOOP while READNEXT ID
GOSUB DO.STUFF
REPEAT
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Allen E. Elwood
Sent: Friday, July 22, 2005 05:34 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [UV] Select Question
Why even have an exit variable, when
@listserver.u2ug.org
Subject: Re: [U2] [UV] Select Question
In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED] writes
>In a message dated 7/13/2005 9:11:23 PM Pacific Daylight Time,
>[EMAIL PROTECTED] writes:
>
>
>> SELECT FILE TO LIST
>> LOOP
>> READNEXT ID FROM
In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED] writes
In a message dated 7/13/2005 9:11:23 PM Pacific Daylight Time,
[EMAIL PROTECTED] writes:
SELECT FILE TO LIST
LOOP
READNEXT ID FROM LIST ELSE ID = @AM
UNTIL ID = @AM DO
REPEAT
SELECT FILE
LOOP
READNEXT ID ELSE ID = @AM
UNTIL ID =
Well, I will admit that I have rarely used the SELECT filevar TO LIST
syntax so I can not pull out a specific example.
However, I have seen several occurrences where SELECT filevar missed
records and when the syntax was changed to EXECUTE "SELECT filename" it
worked perfectly. This has occurre
In a message dated 7/14/05 11:21:14 AM Pacific Daylight Time,
[EMAIL PROTECTED] writes:
<< There can be a major problem with the second syntax depending on what you
are doing to the file. The SELECT filevar syntax does not create a select
list even in memory. It traverses each group in order
Agreed. I only do this only very small utility routines that I need to get
done in 10 minutes or so.
-- Original message --
> In a message dated 7/13/2005 9:11:23 PM Pacific Daylight Time,
> [EMAIL PROTECTED] writes:
>
>
> > SELECT FILE TO LIST
> > LOOP
> > READNE
I'm the "captive" programmer for a system that is just full of the
"infidel EOF" type logic. Said system runs on UniVerse but started
life as an Ultimate application. Since that is all I've ever seen in
the system, that's what I've always used. I'll have to experiment
with the other examples whe
005 11:26 PM
> To: u2-users@listserver.u2ug.org
> Subject: Re: [U2] [UV] Select Question
>
>
> At the risk of starting another debate, I'll toss out my
> preference on internal (or external) READNEXTS.
>
> UD:
> LOOP WHILE READNEXT ID DO
> BLAH
> REPEAT
>
> D
OF DO
BLAH
REPEAT
I have been stung when using the value of the incoming ID as a test value.
Thus I leave it alone.
my 1 cent.
- Original Message -
From: <[EMAIL PROTECTED]>
To: "u2-Users"
Sent: Thursday, July 14, 2005 12:04 AM
Subject: [U2] [UV] Select Question
> Hi a
ginal Message-
> From: [EMAIL PROTECTED] [mailto:owner-u2-
> [EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
> Sent: Thursday, July 14, 2005 12:05 AM
> To: u2-users@listserver.u2ug.org (u2-Users)
> Subject: [U2] [UV] Select Question
>
> Hi all,
>
> Can someone tell me the dife
In a message dated 7/13/2005 9:11:23 PM Pacific Daylight Time,
[EMAIL PROTECTED] writes:
> SELECT FILE TO LIST
> LOOP
> READNEXT ID FROM LIST ELSE ID = @AM
> UNTIL ID = @AM DO
> REPEAT
>
> SELECT FILE
> LOOP
> READNEXT ID ELSE ID = @AM
> UNTIL ID = @AM DO
> REPEAT
I agree that I don't
u2-users@listserver.u2ug.org
Subject: Re: [U2] [UV] Select Question
I'm aware of two differences that may be of importance
- if we're speaking uv -
The LIST alternative is immune to a secondary select
inside the loop - possibly well hidden in an itype in
a subroutine of an subr.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Mats Carlid
Sent: Thursday, July 14, 2005 06:22 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] [UV] Select Question
I'm aware of two differences that may be of importance
- if we're speaking uv -
Selecting to a list variable is a VERY good idea. Personally, I regard
selecting to the default select list in a program as very bad form, and
using a numbered select list as only marginally better. Brian Leach's
response has a good explanation of why, so I won't go into details.
I'm not awa
I'm aware of two differences that may be of importance
- if we're speaking uv -
The LIST alternative is immune to a secondary select
inside the loop - possibly well hidden in an itype in
a subroutine of an subr
The bare select lets the readnext loop start emediately
and saves (probably)
The first syntax is used to ensure isolation of select lists.
It is a good practice to get into, in case someone later on modifies the
code processing whatever you are handling in your selection, especially if
that processing involves calling an external subroutine. Personally I prefer
to use sele
Hi all,
Can someone tell me the diference between the following two examples of
executing an external select?
SELECT FILE TO LIST
LOOP
READNEXT ID FROM LIST ELSE ID = @AM
UNTIL ID = @AM DO
REPEAT
SELECT FILE
LOOP
READNEXT ID ELSE ID = @AM
UNTIL ID = @AM DO
REPEAT
Someone pointed out to
41 matches
Mail list logo
