Re: [U2] [UV] making 00001 our of 1
Mark, I'm one of those programmers who use the overly grand way of spacing you describe. I believe that ASDTFY = '' AS = '' DRT = 0 is much more readable than ASDTFY='' AS='' DRT=0 especially when there is a lot more code than in this example, and everything else around it is crammed together as tightly as it can be as well. Code is written for the human as much as the compiler, and I like it to be as easy to read (and spot errors) as possible. This spacing won't bother a find program if you wrote it or have the source, and teach it better. My 4 cents. Regards, Charlie Noah [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) writes: [snip] P.S. If you use my concept, you may want to have your search strings contain no spaces and convert to the spaces in each reviewed line. There is a overly grand way people program with spaces between operators and even though the complier doesn't care, FIND programs or the editor will miss them if they don't match exactly. My 3 cents. - Original Message - From: Barry Brevik [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) I have always used R%5 but I may miss programs that use other techniques to arrive at the same result. Can someone give me examples that they have seen for changing 1 to 1? I don't want to start a religious war, but I think it is completely normal to use: NBR = NBR 5'0'R or NBR = NBR5'0'R Barry --- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UV] making 00001 our of 1
Chuck, Now if only Jbase had something like VLIST (sigh...). Regards, Charlie Noah [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) writes: Speaking of Y2K-related programs, I too wrote one, but it searched the VLIST of the program. That way I didn't care about spacing, etc.. You might find that method helpful. For example, these 4 source lines compile to the same PCODE: VLIST CDS.BP MARK 1: NBR = NBR 5'0'R 1 0 : 09C format NBR 5'0'R = NBR 2: NBR=NBR5'0'R 2 8 : 09C format NBR 5'0'R = NBR 3: NBR = NBR \5'0'R\ 3 00010 : 09C format NBR 5'0'R = NBR 4: NBR = NBR 5'0'R 4 00018 : 09C format NBR 5'0'R = NBR 5: NBR = FMT( NBR, 5'0'R ) 5 00020 : 09C format NBR 5'0'R = NBR 6 00028 : 190 stop --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UV] making 00001 our of 1
...and also watch out for: 3: A = FMT(5, '60R') 3 0 : 09C format 5 60R = A 4: B = FMT(5, 6'0'R) 4 8 : 09C format 5 6'0'R = B [EMAIL PROTECTED] wrote: Chuck, Now if only Jbase had something like VLIST (sigh...). Regards, Charlie Noah [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) writes: Speaking of Y2K-related programs, I too wrote one, but it searched the VLIST of the program. That way I didn't care about spacing, etc.. You might find that method helpful. For example, these 4 source lines compile to the same PCODE: VLIST CDS.BP MARK 1: NBR = NBR 5'0'R 1 0 : 09C format NBR 5'0'R = NBR 2: NBR=NBR5'0'R 2 8 : 09C format NBR 5'0'R = NBR 3: NBR = NBR \5'0'R\ 3 00010 : 09C format NBR 5'0'R = NBR 4: NBR = NBR 5'0'R 4 00018 : 09C format NBR 5'0'R = NBR 5: NBR = FMT( NBR, 5'0'R ) 5 00020 : 09C format NBR 5'0'R = NBR 6 00028 : 190 stop --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ Send instant messages to your online friends http://uk.messenger.yahoo.com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UV] making 00001 our of 1
Personally I find well spaced and structured code easier to read. Consider the following: BEGIN CASE CASE V=5 TOTAL = AMT*RATE CASE V=6 TOTAL = AMT*RATE2 CASE 1 ERR = 14 END CASE Is much better as: Begin Case Case RateIndicator = 5 TotalAmt = Amount * MainRate Case RateIndicator = 6 TotaAmt = Amount * SecondaryRate Case ELSE ErrorCode = INVALID_RATE_ERROR_CODE End Case Obviously ELSE and INVALID... are equates. Humans can read mixed case a great deal easier than all uppercase and the spacing helps the logic. Sensible variable naming negates the need for comments. All above IMHO and how long will this thread survive before going to community!! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Johnson Sent: 03 March 2005 13:53 To: u2-users@listserver.u2ug.org Subject: Re: [U2] [UV] making 1 our of 1 IMHO I use the term 'overly grand' when i review existing prior code on my current and new clients and there is a very large verbose nature to it. Not being conclusive, but often times the code looks nice but there's way too much 'air' in the program at the expense of being better in the logic area. Certainly I've not read everyone's code. But what I've seen over the years has taught me that when I see grandness, that grandness takes a 200 line program and makes it 700. Case in point: *** * * OPEN MD FILE * *** OPEN ,MD TO F.MD ELSE ERRMSG=CANNOT OPEN THE MD FILE. PLEASE CONTACT YOUR PROGRAMMER GOSUB 9 STOP END * * * OPEN PRODUCT FILE * * OPEN ,PRODUCT TO F.PRODUCT ELSE ERRMSG=CANNOT OPEN THE PRODUCT FILE. PLEASE CONTACT YOUR PROGRAMMER GOSUB 9 STOP END * * END OF OPENING FILES * What gets me is the time spent to make the asterisks match the length of the comments. I see your variable assignment style a lot yet if a new variable were needed, say CUSTOMER.LAST.SALE.DATE = would you re-indent all of the other variables just to look pretty? (I don't mean pretty in a derogatory way, I mean to spend your time and the client's $ for something that really doesn't matter) I know that there are some system-generated source code 4GL's that may create the comments for you. But I can see past that with the inconsistent content of the actual code. There is a command which escapes me now that formats source code (not necessarily databasic) in the editor to match old-school BAL programming. I've tripped over it by accident and then lose my changes as I EXit and then re-edit to not have all the 'air'. Some could argue that a 200 line program becoming 700 could fall under the concept of standardized programming or making it easier for the next guy. Well, I'm that 'next guy' plenty of times and since it's very inconsistent, it's certainly not a standard. I could write a book on the wide variety of programming 'standards' I've inherited and the ineffeciencies found. It's unfortunate that in my travels the grandness happens to have a related brother of reduced logic and a more brute force approach. It's just harder to research with all of that clutter. My 2 cents. Mark Johnson - Original Message - From: [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Thursday, March 03, 2005 6:56 AM Subject: Re: [U2] [UV] making 1 our of 1 Mark, I'm one of those programmers who use the overly grand way of spacing you describe. I believe that ASDTFY = '' AS = '' DRT = 0 is much more readable than ASDTFY='' AS='' DRT=0 especially when there is a lot more code than in this example, and everything else around it is crammed together as tightly as it can be as well. Code is written for the human as much as the compiler, and I like it to be as easy to read (and spot errors) as possible. This spacing won't bother a find program if you wrote it or have the source, and teach it better. My 4 cents. Regards, Charlie Noah [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) writes: [snip] P.S. If you use my concept, you may want to have your search strings contain no spaces and convert to the spaces in each reviewed line. There is a overly grand way people program with spaces between operators and even though the complier doesn't care, FIND programs or the editor will miss them if they don't match exactly. My 3 cents. - Original Message - From: Barry Brevik [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) I have always used R%5 but I may miss programs that use other techniques to arrive at the same result. Can someone give me examples that they have seen for changing 1 to 1? I don't want to start a religious war, but I think
Re: [U2] [UV] making 00001 our of 1
noteI get the digest, am not replying with the actual post/note
It may be that the length is setup as a variable.
i.e R%:ID.LEN
I would search for R%, and the other formats suggested with the thought
that the length is not a constant.
i.e. STR('0', ID.LEN - LEN(ID))
search for STR('0', 'STR(0', etc, etc.
Note this would still allow someone to use a variable for a fill character.
Lastly, are you only checking the (DIR files? I have seen some cases where
includes and inserts are in F type file.
Mike
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UV] making 00001 our of 1
Spacing is overly grand? Though I can't cite specifics, I do recall a study done several years ago that talked about the ergonomic value of whitespace in code. At the risk of misquoting, it seems the brain interprets whitespace as a natural terminator when reading through code, and makes it easier to interpret variable names like ASDTFY or DRT. By contrast, the brain has to manually interpret = as a terminator (and the next statement) and it slows down the overall comprehension. ASDTFY = DRT= When the brain sees the first space after the variable, it understands that the previous whatever-it-is is complete. Then when it sees the equal symbol it can comprehend the meaning of the symbol independently of the variable. Secondly, when assignments (and the like) are aligned like this it tends to reinforce the relationship between the variables, which may be otherwise indirect. By contrast: ASDTFY= DRT= When the brain sees the = after the variable, it has to first sort out an ambiguity. Is this the termination of what was shown prior, or something new? In truth, it's both, and then both have to be processed as equal priority until the brain can establish any other form of precedence to establish which is more important. This is then complicated by the fact that one must read to the end of the statement to determine there is no additional context for establishing precedence, which only complicates the mental process to a greater degree. Also, by having no alignment, there is no relationship implied in the variables, even though they are being assigned in tandem. This further reinforces the ambiguity. So in summary, you can write code as compact as you wish, but understand you do so at the risk of self-imposed (and otherwise unnecessary) mental strain. -Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, March 03, 2005 4:57 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] [UV] making 1 our of 1 Mark, I'm one of those programmers who use the overly grand way of spacing you describe. I believe that ASDTFY = '' AS = '' DRT = 0 is much more readable than ASDTFY='' AS='' DRT=0 especially when there is a lot more code than in this example, and everything else around it is crammed together as tightly as it can be as well. Code is written for the human as much as the compiler, and I like it to be as easy to read (and spot errors) as possible. This spacing won't bother a find program if you wrote it or have the source, and teach it better. My 4 cents. Regards, Charlie Noah [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) writes: [snip] P.S. If you use my concept, you may want to have your search strings contain no spaces and convert to the spaces in each reviewed line. There is a overly grand way people program with spaces between operators and even though the complier doesn't care, FIND programs or the editor will miss them if they don't match exactly. My 3 cents. - Original Message - From: Barry Brevik [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) I have always used R%5 but I may miss programs that use other techniques to arrive at the same result. Can someone give me examples that they have seen for changing 1 to 1? I don't want to start a religious war, but I think it is completely normal to use: NBR = NBR 5'0'R or NBR = NBR5'0'R Barry --- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UV] making 00001 our of 1
That is until you have to add a line and the new lines words are longer which means all the old lines need to be spaced out.. I have better things to do with my time :). I try to follow any acceptable pattern that is already there when changing existing code. But beyond 'tabbing' in if/end statements that are nested and adding simple comments to me anything else is really just a way to spend time. Altho.. would be nice if I could find someone to pay me to type in spaces :). Thanks, Marilyn A. Hilb Value Part, Inc Direct: 847-918-6099 Fax: 847-367-1892 [EMAIL PROTECTED] www.valuepart.com -Original Message- From: Adrian Matthews [mailto:[EMAIL PROTECTED] Sent: Thursday, March 03, 2005 8:55 AM To: u2-users@listserver.u2ug.org Subject:RE: [U2] [UV] making 1 our of 1 Personally I find well spaced and structured code easier to read. Consider the following: BEGIN CASE CASE V=5 TOTAL = AMT*RATE CASE V=6 TOTAL = AMT*RATE2 CASE 1 ERR = 14 END CASE Is much better as: Begin Case Case RateIndicator = 5 TotalAmt = Amount * MainRate Case RateIndicator = 6 TotaAmt = Amount * SecondaryRate Case ELSE ErrorCode = INVALID_RATE_ERROR_CODE End Case Obviously ELSE and INVALID... are equates. Humans can read mixed case a great deal easier than all uppercase and the spacing helps the logic. Sensible variable naming negates the need for comments. All above IMHO and how long will this thread survive before going to community!! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Johnson Sent: 03 March 2005 13:53 To: u2-users@listserver.u2ug.org Subject: Re: [U2] [UV] making 1 our of 1 IMHO I use the term 'overly grand' when i review existing prior code on my current and new clients and there is a very large verbose nature to it. Not being conclusive, but often times the code looks nice but there's way too much 'air' in the program at the expense of being better in the logic area. Certainly I've not read everyone's code. But what I've seen over the years has taught me that when I see grandness, that grandness takes a 200 line program and makes it 700. Case in point: *** * * OPEN MD FILE * *** OPEN ,MD TO F.MD ELSE ERRMSG=CANNOT OPEN THE MD FILE. PLEASE CONTACT YOUR PROGRAMMER GOSUB 9 STOP END * * * OPEN PRODUCT FILE * * OPEN ,PRODUCT TO F.PRODUCT ELSE ERRMSG=CANNOT OPEN THE PRODUCT FILE. PLEASE CONTACT YOUR PROGRAMMER GOSUB 9 STOP END * * END OF OPENING FILES * What gets me is the time spent to make the asterisks match the length of the comments. I see your variable assignment style a lot yet if a new variable were needed, say CUSTOMER.LAST.SALE.DATE = would you re-indent all of the other variables just to look pretty? (I don't mean pretty in a derogatory way, I mean to spend your time and the client's $ for something that really doesn't matter) I know that there are some system-generated source code 4GL's that may create the comments for you. But I can see past that with the inconsistent content of the actual code. There is a command which escapes me now that formats source code (not necessarily databasic) in the editor to match old-school BAL programming. I've tripped over it by accident and then lose my changes as I EXit and then re-edit to not have all the 'air'. Some could argue that a 200 line program becoming 700 could fall under the concept of standardized programming or making it easier for the next guy. Well, I'm that 'next guy' plenty of times and since it's very inconsistent, it's certainly not a standard. I could write a book on the wide variety of programming 'standards' I've inherited and the ineffeciencies found. It's unfortunate that in my travels the grandness happens to have a related brother of reduced logic and a more brute force approach. It's just harder to research with all of that clutter. My 2 cents. Mark Johnson - Original Message - From: [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Thursday, March 03, 2005 6:56 AM Subject: Re: [U2] [UV] making 1 our of 1 Mark, I'm one of those programmers who use the overly grand way of spacing you describe. I believe that ASDTFY = '' AS = '' DRT = 0 is much more readable than ASDTFY='' AS='' DRT=0 especially when there is a lot more code than in this example, and everything else around it is crammed together as tightly as it can be as well. Code is written for the human as much as the compiler, and I like it to be as easy to read (and spot errors) as possible. This spacing won't bother a find program if you wrote it or have the source
RE: [U2] [UV] making 00001 our of 1
I don't like to disagree with people BUT.. I like the first example best. Why not compare like with like This is how I would write it BEGIN CASE CASE RATE.INDICATOR = 5 TOTAL.AMT = AMOUNT * MAIN.RATE CASE RATE.INDICATOR = 6 TOTAL.AMT = AMOUNT * SECONDARY.RATE CASE 1 ERROR.CODE = INVALID.RATE.ERROR.CODE END CASE We each have our own style. They are all just as good as each other. It's just what you are used to. Les. -Original Message- From: Adrian Matthews [mailto:[EMAIL PROTECTED] Sent: 03 March 2005 14:55 To: u2-users@listserver.u2ug.org Subject: RE: [U2] [UV] making 1 our of 1 Personally I find well spaced and structured code easier to read. Consider the following: BEGIN CASE CASE V=5 TOTAL = AMT*RATE CASE V=6 TOTAL = AMT*RATE2 CASE 1 ERR = 14 END CASE Is much better as: Begin Case Case RateIndicator = 5 TotalAmt = Amount * MainRate Case RateIndicator = 6 TotaAmt = Amount * SecondaryRate Case ELSE ErrorCode = INVALID_RATE_ERROR_CODE End Case Obviously ELSE and INVALID... are equates. Humans can read mixed case a great deal easier than all uppercase and the spacing helps the logic. Sensible variable naming negates the need for comments. All above IMHO and how long will this thread survive before going to community!! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Johnson Sent: 03 March 2005 13:53 To: u2-users@listserver.u2ug.org Subject: Re: [U2] [UV] making 1 our of 1 IMHO I use the term 'overly grand' when i review existing prior code on my current and new clients and there is a very large verbose nature to it. Not being conclusive, but often times the code looks nice but there's way too much 'air' in the program at the expense of being better in the logic area. Certainly I've not read everyone's code. But what I've seen over the years has taught me that when I see grandness, that grandness takes a 200 line program and makes it 700. Case in point: *** * * OPEN MD FILE * *** OPEN ,MD TO F.MD ELSE ERRMSG=CANNOT OPEN THE MD FILE. PLEASE CONTACT YOUR PROGRAMMER GOSUB 9 STOP END * * * OPEN PRODUCT FILE * * OPEN ,PRODUCT TO F.PRODUCT ELSE ERRMSG=CANNOT OPEN THE PRODUCT FILE. PLEASE CONTACT YOUR PROGRAMMER GOSUB 9 STOP END * * END OF OPENING FILES * What gets me is the time spent to make the asterisks match the length of the comments. I see your variable assignment style a lot yet if a new variable were needed, say CUSTOMER.LAST.SALE.DATE = would you re-indent all of the other variables just to look pretty? (I don't mean pretty in a derogatory way, I mean to spend your time and the client's $ for something that really doesn't matter) I know that there are some system-generated source code 4GL's that may create the comments for you. But I can see past that with the inconsistent content of the actual code. There is a command which escapes me now that formats source code (not necessarily databasic) in the editor to match old-school BAL programming. I've tripped over it by accident and then lose my changes as I EXit and then re-edit to not have all the 'air'. Some could argue that a 200 line program becoming 700 could fall under the concept of standardized programming or making it easier for the next guy. Well, I'm that 'next guy' plenty of times and since it's very inconsistent, it's certainly not a standard. I could write a book on the wide variety of programming 'standards' I've inherited and the ineffeciencies found. It's unfortunate that in my travels the grandness happens to have a related brother of reduced logic and a more brute force approach. It's just harder to research with all of that clutter. My 2 cents. Mark Johnson - Original Message - From: [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Thursday, March 03, 2005 6:56 AM Subject: Re: [U2] [UV] making 1 our of 1 Mark, I'm one of those programmers who use the overly grand way of spacing you describe. I believe that ASDTFY = '' AS = '' DRT = 0 is much more readable than ASDTFY='' AS='' DRT=0 especially when there is a lot more code than in this example, and everything else around it is crammed together as tightly as it can be as well. Code is written for the human as much as the compiler, and I like it to be as easy to read (and spot errors) as possible. This spacing won't bother a find program if you wrote it or have the source, and teach it better. My 4 cents. Regards, Charlie Noah [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) writes: [snip] P.S. If you use my concept, you may
RE: [U2] [UV] making 00001 our of 1
A number of years ago I knew a guy who avoided using = as both assignment and conditional, preferring to use = only for assignment and EQ for conditions. His rationale, which I agree with, was that it removes ambiguity and forces spaces around the EQ to improve readability. That was probably 12 years ago at least, and I still try to do that today because once you get used it it, it really does improve readability, particularly months after the original implementation. -Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Les Hewkin Sent: Thursday, March 03, 2005 9:05 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] [UV] making 1 our of 1 I don't like to disagree with people BUT.. I like the first example best. Why not compare like with like This is how I would write it BEGIN CASE CASE RATE.INDICATOR = 5 TOTAL.AMT = AMOUNT * MAIN.RATE CASE RATE.INDICATOR = 6 TOTAL.AMT = AMOUNT * SECONDARY.RATE CASE 1 ERROR.CODE = INVALID.RATE.ERROR.CODE END CASE We each have our own style. They are all just as good as each other. It's just what you are used to. Les. -Original Message- From: Adrian Matthews [mailto:[EMAIL PROTECTED] Sent: 03 March 2005 14:55 To: u2-users@listserver.u2ug.org Subject: RE: [U2] [UV] making 1 our of 1 Personally I find well spaced and structured code easier to read. Consider the following: BEGIN CASE CASE V=5 TOTAL = AMT*RATE CASE V=6 TOTAL = AMT*RATE2 CASE 1 ERR = 14 END CASE Is much better as: Begin Case Case RateIndicator = 5 TotalAmt = Amount * MainRate Case RateIndicator = 6 TotaAmt = Amount * SecondaryRate Case ELSE ErrorCode = INVALID_RATE_ERROR_CODE End Case Obviously ELSE and INVALID... are equates. Humans can read mixed case a great deal easier than all uppercase and the spacing helps the logic. Sensible variable naming negates the need for comments. All above IMHO and how long will this thread survive before going to community!! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Johnson Sent: 03 March 2005 13:53 To: u2-users@listserver.u2ug.org Subject: Re: [U2] [UV] making 1 our of 1 IMHO I use the term 'overly grand' when i review existing prior code on my current and new clients and there is a very large verbose nature to it. Not being conclusive, but often times the code looks nice but there's way too much 'air' in the program at the expense of being better in the logic area. Certainly I've not read everyone's code. But what I've seen over the years has taught me that when I see grandness, that grandness takes a 200 line program and makes it 700. Case in point: *** * * OPEN MD FILE * *** OPEN ,MD TO F.MD ELSE ERRMSG=CANNOT OPEN THE MD FILE. PLEASE CONTACT YOUR PROGRAMMER GOSUB 9 STOP END * * * OPEN PRODUCT FILE * * OPEN ,PRODUCT TO F.PRODUCT ELSE ERRMSG=CANNOT OPEN THE PRODUCT FILE. PLEASE CONTACT YOUR PROGRAMMER GOSUB 9 STOP END * * END OF OPENING FILES * What gets me is the time spent to make the asterisks match the length of the comments. I see your variable assignment style a lot yet if a new variable were needed, say CUSTOMER.LAST.SALE.DATE = would you re-indent all of the other variables just to look pretty? (I don't mean pretty in a derogatory way, I mean to spend your time and the client's $ for something that really doesn't matter) I know that there are some system-generated source code 4GL's that may create the comments for you. But I can see past that with the inconsistent content of the actual code. There is a command which escapes me now that formats source code (not necessarily databasic) in the editor to match old-school BAL programming. I've tripped over it by accident and then lose my changes as I EXit and then re-edit to not have all the 'air'. Some could argue that a 200 line program becoming 700 could fall under the concept of standardized programming or making it easier for the next guy. Well, I'm that 'next guy' plenty of times and since it's very inconsistent, it's certainly not a standard. I could write a book on the wide variety of programming 'standards' I've inherited and the ineffeciencies found. It's unfortunate that in my travels the grandness happens to have a related brother of reduced logic and a more brute force approach. It's just harder to research with all of that clutter. My 2 cents. Mark Johnson - Original Message - From: [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Thursday, March 03, 2005 6:56 AM Subject: Re: [U2] [UV
[U2] [UV] making 00001 our of 1 - THANKS AND SORRY
I just wanted to say thanks to everyone who responded to my question. Basically, I was looking to find any code in our system that could possibly be adding leading 0's to our item number since we are converting from a fixed 5 digit item number to a variable length number. With the help of the list (once again), I can file another project away in the success drawer. Thanks very much to all! I also wanted to say that I am sorry for starting any holy wars. Oh yeah, and Kevin... While I would agree from reading many of your posts that you are an extemely sharp individual, I have to tell you that it is really irritating to people to hear others refer to themselves in the third person (ie. the brain). Or... Did I misunderstand yet another e-mail. Haha JK Thanks, Scott -- Original message -- Spacing is overly grand? Though I can't cite specifics, I do recall a study done several years ago that talked about the ergonomic value of whitespace in code. At the risk of misquoting, it seems the brain interprets whitespace as a natural terminator when reading through code, and makes it easier to interpret variable names like ASDTFY or DRT. By contrast, the brain has to manually interpret = as a terminator (and the next statement) and it slows down the overall comprehension. ASDTFY = DRT = When the brain sees the first space after the variable, it understands that the previous whatever-it-is is complete. Then when it sees the equal symbol it can comprehend the meaning of the symbol independently of the variable. Secondly, when assignments (and the like) are aligned like this it tends to reinforce the relationship between the variables, which may be otherwise indirect. By contrast: ASDTFY= DRT= When the brain sees the = after the variable, it has to first sort out an ambiguity. Is this the termination of what was shown prior, or something new? In truth, it's both, and then both have to be processed as equal priority until the brain can establish any other form of precedence to establish which is more important. This is then complicated by the fact that one must read to the end of the statement to determine there is no additional context for establishing precedence, which only complicates the mental process to a greater degree. Also, by having no alignment, there is no relationship implied in the variables, even though they are being assigned in tandem. This further reinforces the ambiguity. So in summary, you can write code as compact as you wish, but understand you do so at the risk of self-imposed (and otherwise unnecessary) mental strain. -Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, March 03, 2005 4:57 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] [UV] making 1 our of 1 Mark, I'm one of those programmers who use the overly grand way of spacing you describe. I believe that ASDTFY = '' AS = '' DRT = 0 is much more readable than ASDTFY='' AS='' DRT=0 especially when there is a lot more code than in this example, and everything else around it is crammed together as tightly as it can be as well. Code is written for the human as much as the compiler, and I like it to be as easy to read (and spot errors) as possible. This spacing won't bother a find program if you wrote it or have the source, and teach it better. My 4 cents. Regards, Charlie Noah [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) writes: [snip] P.S. If you use my concept, you may want to have your search strings contain no spaces and convert to the spaces in each reviewed line. There is a overly grand way people program with spaces between operators and even though the complier doesn't care, FIND programs or the editor will miss them if they don't match exactly. My 3 cents. - Original Message - From: Barry Brevik [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) I have always used R%5 but I may miss programs that use other techniques to arrive at the same result. Can someone give me examples that they have seen for changing 1 to 1? I don't want to start a religious war, but I think it is completely normal to use: NBR = NBR 5'0'R or NBR = NBR5'0'R Barry --- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UV] making 00001 our of 1 - THANKS AND SORRY
I don't think he was referring to himself. He was just stating what the research on this issue determined.. referring to the brain as simply the human brain. Not his in particular. :). Thanks, Marilyn A. Hilb Value Part, Inc Direct: 847-918-6099 Fax: 847-367-1892 [EMAIL PROTECTED] www.valuepart.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, March 03, 2005 11:49 AM To: u2-users@listserver.u2ug.org Subject:[U2] [UV] making 1 our of 1 - THANKS AND SORRY I just wanted to say thanks to everyone who responded to my question. Basically, I was looking to find any code in our system that could possibly be adding leading 0's to our item number since we are converting from a fixed 5 digit item number to a variable length number. With the help of the list (once again), I can file another project away in the success drawer. Thanks very much to all! I also wanted to say that I am sorry for starting any holy wars. Oh yeah, and Kevin... While I would agree from reading many of your posts that you are an extemely sharp individual, I have to tell you that it is really irritating to people to hear others refer to themselves in the third person (ie. the brain). Or... Did I misunderstand yet another e-mail. Haha JK Thanks, Scott -- Original message -- Spacing is overly grand? Though I can't cite specifics, I do recall a study done several years ago that talked about the ergonomic value of whitespace in code. At the risk of misquoting, it seems the brain interprets whitespace as a natural terminator when reading through code, and makes it easier to interpret variable names like ASDTFY or DRT. By contrast, the brain has to manually interpret = as a terminator (and the next statement) and it slows down the overall comprehension. ASDTFY = DRT = When the brain sees the first space after the variable, it understands that the previous whatever-it-is is complete. Then when it sees the equal symbol it can comprehend the meaning of the symbol independently of the variable. Secondly, when assignments (and the like) are aligned like this it tends to reinforce the relationship between the variables, which may be otherwise indirect. By contrast: ASDTFY= DRT= When the brain sees the = after the variable, it has to first sort out an ambiguity. Is this the termination of what was shown prior, or something new? In truth, it's both, and then both have to be processed as equal priority until the brain can establish any other form of precedence to establish which is more important. This is then complicated by the fact that one must read to the end of the statement to determine there is no additional context for establishing precedence, which only complicates the mental process to a greater degree. Also, by having no alignment, there is no relationship implied in the variables, even though they are being assigned in tandem. This further reinforces the ambiguity. So in summary, you can write code as compact as you wish, but understand you do so at the risk of self-imposed (and otherwise unnecessary) mental strain. -Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, March 03, 2005 4:57 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] [UV] making 1 our of 1 Mark, I'm one of those programmers who use the overly grand way of spacing you describe. I believe that ASDTFY = '' AS = '' DRT = 0 is much more readable than ASDTFY='' AS='' DRT=0 especially when there is a lot more code than in this example, and everything else around it is crammed together as tightly as it can be as well. Code is written for the human as much as the compiler, and I like it to be as easy to read (and spot errors) as possible. This spacing won't bother a find program if you wrote it or have the source, and teach it better. My 4 cents. Regards, Charlie Noah [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) writes: [snip] P.S. If you use my concept, you may want to have your search strings contain no spaces and convert to the spaces in each reviewed line. There is a overly grand way people program with spaces between operators and even though the complier doesn't care, FIND programs or the editor will miss them if they don't match exactly. My 3 cents. - Original Message - From: Barry Brevik [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) I have always used R%5 but I may miss programs that use other techniques to arrive at the same result. Can someone give me examples that they have seen for changing 1 to 1? I don't want to start a religious war, but I think it is completely normal to use: NBR = NBR 5'0'R
RE: [U2] [UV] making 00001 our of 1 - THANKS AND SORRY
Folks, snip refer to themselves in the third person (ie. the brain). Or... Did I misunderstand yet another e-mail. Haha JK Did ya notice the Haha JK (as in just kidding)? He was intentionally misunderstanding so as to be funny. --Ron P. P.S. an End-of-thread is probably in order :) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marilyn Hilb Sent: Thursday, March 03, 2005 12:20 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] [UV] making 1 our of 1 - THANKS AND SORRY I don't think he was referring to himself. He was just stating what the research on this issue determined.. referring to the brain as simply the human brain. Not his in particular. :). Thanks, Marilyn A. Hilb Value Part, Inc Direct: 847-918-6099 Fax: 847-367-1892 [EMAIL PROTECTED] www.valuepart.com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UV] making 00001 our of 1 - THANKS AND SORRY
Agreed, Ron. END OF THREAD. - Charles Barouch, Moderator Pingilley, Ron wrote: P.S. an End-of-thread is probably in order :) --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UV] making 00001 our of 1 - THANKS AND SORRY
w I was trying to make a joke. Sorry. Not about the extemely sharp individual part though - I was sincere. I would never insult anyone on this list as it is an incredibly valuable resource for me. And... I enjoy reading from people who have great knowledge and a passion for what they do. Sorry for any offense taken. I assumed it would be obvious that I was joking. Once again though, thanks for all of the help. -- Original message -- Oh, absolutely you misunderstood! Reference to the brain was not a reference to an individual or self, but rather that amorphous mass of grey matter that sits between the ears of each of us. Understanding how this mass works -- if only in the slightest way -- can be useful information in leveraging that mass more effectively. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, March 03, 2005 10:49 AM To: u2-users@listserver.u2ug.org Subject: [U2] [UV] making 1 our of 1 - THANKS AND SORRY I just wanted to say thanks to everyone who responded to my question. Basically, I was looking to find any code in our system that could possibly be adding leading 0's to our item number since we are converting from a fixed 5 digit item number to a variable length number. With the help of the list (once again), I can file another project away in the success drawer. Thanks very much to all! I also wanted to say that I am sorry for starting any holy wars. Oh yeah, and Kevin... While I would agree from reading many of your posts that you are an extemely sharp individual, I have to tell you that it is really irritating to people to hear others refer to themselves in the third person (ie. the brain). Or... Did I misunderstand yet another e-mail. Haha JK Thanks, Scott -- Original message -- Spacing is overly grand? Though I can't cite specifics, I do recall a study done several years ago that talked about the ergonomic value of whitespace in code. At the risk of misquoting, it seems the brain interprets whitespace as a natural terminator when reading through code, and makes it easier to interpret variable names like ASDTFY or DRT. By contrast, the brain has to manually interpret = as a terminator (and the next statement) and it slows down the overall comprehension. ASDTFY = DRT = When the brain sees the first space after the variable, it understands that the previous whatever-it-is is complete. Then when it sees the equal symbol it can comprehend the meaning of the symbol independently of the variable. Secondly, when assignments (and the like) are aligned like this it tends to reinforce the relationship between the variables, which may be otherwise indirect. By contrast: ASDTFY= DRT= When the brain sees the = after the variable, it has to first sort out an ambiguity. Is this the termination of what was shown prior, or something new? In truth, it's both, and then both have to be processed as equal priority until the brain can establish any other form of precedence to establish which is more important. This is then complicated by the fact that one must read to the end of the statement to determine there is no additional context for establishing precedence, which only complicates the mental process to a greater degree. Also, by having no alignment, there is no relationship implied in the variables, even though they are being assigned in tandem. This further reinforces the ambiguity. So in summary, you can write code as compact as you wish, but understand you do so at the risk of self-imposed (and otherwise unnecessary) mental strain. -Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, March 03, 2005 4:57 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] [UV] making 1 our of 1 Mark, I'm one of those programmers who use the overly grand way of spacing you describe. I believe that ASDTFY = '' AS = '' DRT = 0 is much more readable than ASDTFY='' AS='' DRT=0 especially when there is a lot more code than in this example, and everything else around it is crammed together as tightly as it can be as well. Code is written for the human as much as the compiler, and I like it to be as easy to read (and spot errors) as possible. This spacing won't bother a find program if you wrote it or have the source, and teach it better. My 4 cents. Regards, Charlie Noah [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) writes: [snip] P.S. If you use my concept, you may want to have your search strings
[U2] [UV] making 00001 our of 1
Hi all, I have a need to search through our program files for any code that format a number from 1 through 9 with leading 0's. I have always used R%5 but I may miss programs that use other techniques to arrive at the same result. Can someone give me examples that they have seen for changing 1 to 1? Thanks much, Scott --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UV] making 00001 our of 1
I've seen: (0:VARNAME)[5] on UniVerse to do that. Ugly, but works. --Ron P. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, March 02, 2005 3:30 PM To: u2-Users Subject: [U2] [UV] making 1 our of 1 Hi all, I have a need to search through our program files for any code that format a number from 1 through 9 with leading 0's. I have always used R%5 but I may miss programs that use other techniques to arrive at the same result. Can someone give me examples that they have seen for changing 1 to 1? Thanks much, Scott --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UV] making 00001 our of 1
... = variableR%5 ... = OCONV(variable,'MR%5') variable = '0' : variable variable = variable[LEN(variable) - 4,5] Just a few I've seen over the years. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, March 02, 2005 2:30 PM To: u2-Users Subject: [U2] [UV] making 1 our of 1 Hi all, I have a need to search through our program files for any code that format a number from 1 through 9 with leading 0's. I have always used R%5 but I may miss programs that use other techniques to arrive at the same result. Can someone give me examples that they have seen for changing 1 to 1? Thanks much, Scott --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UV] making 00001 our of 1
X = ('0':X) R#5
Bruce M Neylon
Health Care Management Group
[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
03/02/2005 04:30 PM
Please respond to u2-users
To: u2-users@listserver.u2ug.org (u2-Users)
cc:
Subject:[U2] [UV] making 1 our of 1
Hi all,
I have a need to search through our program files for any code that format
a number from 1 through 9 with leading 0's.
I have always used R%5 but I may miss programs that use other techniques
to arrive at the same result. Can someone give me examples that they have
seen for changing 1 to 1?
Thanks much,
Scott
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UV] making 00001 our of 1
FMT(VAR,'R05') works under UD, not sure about UV Larry Hiscock Western Computer Services -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, March 02, 2005 1:30 PM To: u2-Users Subject: [U2] [UV] making 1 our of 1 Hi all, I have a need to search through our program files for any code that format a number from 1 through 9 with leading 0's. I have always used R%5 but I may miss programs that use other techniques to arrive at the same result. Can someone give me examples that they have seen for changing 1 to 1? Thanks much, Scott --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UV] making 00001 our of 1
And (0:Var)[len(Var-4),5] Pingilley, Ron wrote: I've seen: (0:VARNAME)[5] on UniVerse to do that. Ugly, but works. --Ron P. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, March 02, 2005 3:30 PM To: u2-Users Subject: [U2] [UV] making 1 our of 1 Hi all, I have a need to search through our program files for any code that format a number from 1 through 9 with leading 0's. I have always used R%5 but I may miss programs that use other techniques to arrive at the same result. Can someone give me examples that they have seen for changing 1 to 1? Thanks much, Scott --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UV] making 00001 our of 1
I have seen X=(X+100)[2,5] [EMAIL PROTECTED] wrote: Hi all, I have a need to search through our program files for any code that format a number from 1 through 9 with leading 0's. I have always used R%5 but I may miss programs that use other techniques to arrive at the same result. Can someone give me examples that they have seen for changing 1 to 1? Thanks much, Scott --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UV] making 00001 our of 1
fmt(var, R%5) Kevin King wrote: ... = variableR%5 ... = OCONV(variable,'MR%5') variable = '0' : variable variable = variable[LEN(variable) - 4,5] Just a few I've seen over the years. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UV] making 00001 our of 1
Scott wrote on 03/02/2005 04:30:09 PM: I have a need to search through our program files for any code that format a number from 1 through 9 with leading 0's. It's nasty, and I don't recommend it, but I've seen people do things like this: LOOP WHILE LEN(X) LT 5 DO X = 0 : X REPEAT Actually, this is generally done with some ugly GOTO logic, but I just couldn't make myself do that. Of course, it could be done with a FOR-NEXT loop, or any variety of ways. Good luck trying to automate a search for this sort of thing. Tim Snyder Consulting I/T Specialist , U2 Professional Services North American Lab Services DB2 Information Management, IBM Software Group 717-545-6403 [EMAIL PROTECTED] --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UV] making 00001 our of 1
Goo'day, X = STR(0,5-LEN(X)):X At 21:30 02/03/05 +, you wrote: Hi all, I have a need to search through our program files for any code that format a number from 1 through 9 with leading 0's. I have always used R%5 but I may miss programs that use other techniques to arrive at the same result. Can someone give me examples that they have seen for changing 1 to 1? Thanks much, Scott --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.5.7 - Release Date: 01/03/05 -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.5.7 - Release Date: 01/03/05 Regards, Bruce Nichol Talon Computer Services ALBURYNSW 2640 Australia http://www.taloncs.com.au Tel: +61 (0)411149636 Fax: +61 (0)260232119 If it ain't broke, fix it till it is! -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.5.7 - Release Date: 01/03/05 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.5.7 - Release Date: 01/03/05 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UV] making 00001 our of 1
Try X=1 Y=LEN(X) Z=STR(0,4-Y):X HTH [EMAIL PROTECTED] 03/02/05 01:30PM Hi all, I have a need to search through our program files for any code that format a number from 1 through 9 with leading 0's. I have always used R%5 but I may miss programs that use other techniques to arrive at the same result. Can someone give me examples that they have seen for changing 1 to 1? Thanks much, Scott --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UV] making 00001 our of 1
Format 5'0'R is quite common.
I've also seen Str('0',5-Len(TheNumber)):TheNumber as a technique.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UV] making 00001 our of 1
Scott, If the real goal is to screen out updates to files with leading zeroes, you might want to put triggers on the files you need to check and see when/how the updates are occurring. - Chuck Zero as a Leader Barouch Lee Beel wrote: Try X=1 Y=LEN(X) Z=STR(0,4-Y):X HTH [EMAIL PROTECTED] 03/02/05 01:30PM Hi all, I have a need to search through our program files for any code that format a number from 1 through 9 with leading 0's. I have always used R%5 but I may miss programs that use other techniques to arrive at the same result. Can someone give me examples that they have seen for changing 1 to 1? Thanks much, Scott --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UV] making 00001 our of 1
I have always used R%5 but I may miss programs that use other techniques to arrive at the same result. Can someone give me examples that they have seen for changing 1 to 1? I don't want to start a religious war, but I think it is completely normal to use: NBR = NBR 5'0'R or NBR = NBR5'0'R Barry --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [UV] making 00001 our of 1
Despite the replies for the various forms of R%5, there may be some more yet offered. This reminds me of the Y2K reviews I had to apply in 1998-1999 before the sky fell. I wrote a program who's concept may help in this pursuit. From the Y2K era, there were certain date oriented things to look for in databasic programs. The generic FIND or SEARCH programs could essentially SELECT the proper programs to manually review but then you had to view the code in the editor and deal with a few false positives. This utility prompts for a file name (BP) and one or more OR'd strings to search for. The joy of this utility is that it would find the item in question and display the previous 3 and following 3 lines of code so you could see the context of the sought string and not just the single line with that string. You could send the output to the screen or printer. That's my suggestion for finding something that's not easily identified. P.S. If you use my concept, you may want to have your search strings contain no spaces and convert to the spaces in each reviewed line. There is a overly grand way people program with spaces between operators and even though the complier doesn't care, FIND programs or the editor will miss them if they don't match exactly. My 3 cents. - Original Message - From: Barry Brevik [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Wednesday, March 02, 2005 9:32 PM Subject: RE: [U2] [UV] making 1 our of 1 I have always used R%5 but I may miss programs that use other techniques to arrive at the same result. Can someone give me examples that they have seen for changing 1 to 1? I don't want to start a religious war, but I think it is completely normal to use: NBR = NBR 5'0'R or NBR = NBR5'0'R Barry --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [UV] making 00001 our of 1
Speaking of Y2K-related programs, I too wrote one, but it searched the VLIST of the program. That way I didn't care about spacing, etc.. You might find that method helpful. For example, these 4 source lines compile to the same PCODE: VLIST CDS.BP MARK 1: NBR = NBR 5'0'R 1 0 : 09C format NBR 5'0'R = NBR 2: NBR=NBR5'0'R 2 8 : 09C format NBR 5'0'R = NBR 3: NBR = NBR \5'0'R\ 3 00010 : 09C format NBR 5'0'R = NBR 4: NBR = NBR 5'0'R 4 00018 : 09C format NBR 5'0'R = NBR 5: NBR = FMT( NBR, 5'0'R ) 5 00020 : 09C format NBR 5'0'R = NBR 6 00028 : 190 stop -Original Message- From: Mark Johnson ... This reminds me of the Y2K reviews I had to apply in 1998-1999 before the sky fell. I wrote a program who's concept may help in this pursuit... - Original Message - From: Barry Brevik [EMAIL PROTECTED] NBR = NBR 5'0'R or NBR = NBR5'0'R --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
