Mark: Remember, all computer languages operate within their own limitations. In the early stages of mvDbms computing small speed tricks were necessary when one ran 50 users on a 1MB memory machine. Now, it only matters with batch processing (as you've seen with REMOVE).
I don't think it is necessary to limit our logical thinking by the limitations of the computing environment we're working with, which we see every day. :-) Bill > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Mark Johnson > Sent: Friday, August 12, 2005 9:18 PM > To: [email protected] > Subject: Re: [Maybe spam] RE: [U2] Remove Scenario > > Not for nothin' but I believe there's more to the variable > assignment version of an equate than you've expressed. > > In essence, there are 2 kinds of EQUATES. The first style, > sometimes known as an alias, is like your > > EQUATE APFILE.BALDUE TO APFILE.REC(2) > > and you can manage the contents of the second field in the > A/P record either using the left portion of the TO or the right. > > The second style is more on the compiler level and not a > simple variable assignment. > > EQUATE TRUE TO 1 > > causes the compiler to replace the expression TRUE inside the > source code with the literal value '1'. Then it compiles. > This is different than [the rest snipped] ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
