What compile arguments? I just checked the help pages for both BASIC and RAID and don't see anything about including the INCLUDE code so the debugger can use it.
-----Original Message----- From: David A. Green <[email protected]> To: 'U2 Users List' <[email protected]> Sent: Wed, Feb 8, 2012 6:21 am Subject: Re: [U2] Including Code - A Best Practice? I don't think using an INCLUDE is bad, but it must be done in the right way. Pros: * It is the fastest way to use reusable code. It can be debugged just fine if you use the correct compile arguments. Cons: * You must, MUST, address the variable names. I always prefix mine with ODE$NAME where CODE is the prefix I've chosen for my INCLUDE and should be nique for your system. You must recompile all instances if you want the change to be updated verywhere. More difficult to edit program logic, unless you have a nice editor that rings in INCLUDES/INSERTS for you automatically. David A. Green 480) 813-1725 AG Consulting -----Original Message----- rom: [email protected] mailto:[email protected]] On Behalf Of Baker Hughes ent: Tuesday, February 07, 2012 4:05 PM o: U2 Users List ([email protected]) ubject: [U2] Including Code - A Best Practice? A friendly discussion arose recently among some U2/MV Developers about hether to include code. If any of you have opinions about the positive aspects or negative aspects f this practice, please respond. Should it be adopted as a best practice, r rejected as special situation use only? Many shops probably include long sections of variable assignments, or erhaps globally opened files. This is pretty much accepted everywhere as a ood practice. In question here is the insertion of actual code - business logic or screen /O programs or code snippets. Maybe you know of methods to overcome some of the obvious downsides: nintended reassignment of local variables, difficulty in debugging, others. What are the positive upsides? Performance gains? What is the longest snippet you think should be included, if allowed? What advantage has included code over a CALL or a Function? Reuse. What lse? Can the downsides be mitigated satisfactorily to justify the gains? Thanks so much. -Baker ________________________________ his communication, its contents and any file attachments transmitted with t are intended solely for the addressee(s) and may contain confidential roprietary information. ccess by any other party without the express written permission of the ender is STRICTLY PROHIBITED. f you have received this communication in error you may not copy, istribute or use the contents, attachments or information in any way. lease destroy it and contact the sender. ______________________________________________ 2-Users mailing list [email protected] ttp://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ 2-Users mailing list [email protected] ttp://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
