Just DON'T start a few flame wars over this :-) I'd actually vehemently disagree with the original suggestion, for several reasons. The two biggest are:
It introduces an extra variable. Any poor maintenance guy coming along has to worry about whether it's used elsewhere. This sort of behaviour is actually frowned on in ANY programming language, I believe. And my personal reason for disliking it, over and above the previous - it takes two lines where one would do. Okay, compressing code for the sake of it can hinder comprehension, but I like tight, compact code with white-space separating small sections, not individual sections full of white space... Cheers, Wol -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Baker Hughes Sent: 19 November 2007 15:18 To: u2-users@listserver.u2ug.org Subject: RE: [U2] OCONV Extraction Question - Best Practises It's JUST a preference, presently.... I know we all reach for a good balance between brevity and clarity. I have some preferences too which I think are ideal, which seem less than ideal to others. ... but rather than mount my own hobby horse I have a suggestion / question that could put these types of exchanges to rest: WHAT IF - the U2UG took it as a future project to compile a Best Practices coding guideline document for our language? There's always helpful 'How to' stuff exchanged here. ...but style question sometimes spiral downward. As someone pointed out recently, we have the blessing and curse of using a rather free style language. Not much Structure-Style is not imposed by the construct of the language itself, like some others. Is it time to codify some best practices relating to structure, modularity, reuse, length of internal subs, etc? I may not like some of the resulting definitions myself but it would build cohesion and greater respect for the MV space. Another thing it would do is chart a clearer path for those coming behind us - we need new blood if the VARs in this space are going to continue to sell/support embedded MV apps. I would personally find it fascinating to see some of our venerable coders get together and see what they produced along this line. I have some names in mind but I'll wait for the nominations to officially open. Happy Thanksgiving. -Baker -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of MAJ Programming Sent: Saturday, November 17, 2007 12:58 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] OCONV Extraction Question According to who? I know there are some pluses and minuses but where is this decided or is it just a preference. Thanks Mark Johnson ----- Original Message ----- From: "Brutzman, Bill" <[EMAIL PROTECTED]> To: <u2-users@listserver.u2ug.org> Sent: Friday, November 16, 2007 11:30 AM Subject: RE: [U2] OCONV Extraction Question > Speaking of mis-used commands and side-stepping some of the given code > craziness... > > It is better practice to atomize the code into discrete elements such as... > > Var1.F = oconv(Var1, 'MD0') > crt Var1.F 'R#11' > > rather than to try to kill two birds with one stone by including an > oconv statement inside a crt statement such as... > > crt oconv(Var1, 'MD0') > > --Bill > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of MAJ > Programming > Sent: Friday, November 16, 2007 12:48 AM > To: u2-users@listserver.u2ug.org > Subject: Re: [U2] OCONV Extraction Question > > > This is real smart, making things harder than they should be. Just use <>. > > Mark Johnson > ----- Original Message ----- > From: <[EMAIL PROTECTED]> > To: <u2-users@listserver.u2ug.org> > Sent: Wednesday, November 14, 2007 5:23 PM > Subject: RE: [U2] OCONV Extraction Question > > > > Didn't work for me either. It may not fit what you need, but SWAP > > can make > > it work. > > > > VAR1 = 'SAM':@VM:'TRUDY' > > SWAP @VM WITH '*' IN VAR1 > > FMTSTR = 'G*1' > > CRT OCONV(VAR1,FMTSTR) > > > > Brad > > > > > > U.S. BANCORP made the following annotations > > -------------------------------------------------------------------- > > - Electronic Privacy Notice. This e-mail, and any attachments, > > contains > information that is, or may be, covered by electronic communications privacy > laws, and is also confidential and proprietary in nature. If you are > not the > intended recipient, please be advised that you are legally prohibited > from retaining, using, copying, distributing, or otherwise disclosing > this information in any manner. Instead, please reply to the sender > that you have > received this communication in error, and then immediately delete it. Thank > you in advance for your cooperation. > > > > > > > > -------------------------------------------------------------------- > > - > > ------- > > 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/ ------- 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/
