An include is fine for declarations, but not for executable code due to the
fact that individual lines in the include cannot be debugged (on Unidata).
 Declarations like EQUates and common blocks are best uses for includes.
 The need to break apart big routines due to some arbitrary limit (i.e.
32K) is no longer a valid argument and without the ability to debug
included code, any gains quickly become lost.

On Tue, Feb 7, 2012 at 4:04 PM, Baker Hughes <baker.hug...@mouser.com>wrote:

> A friendly discussion arose recently among some U2/MV Developers about
> whether to include code.
>
> If any of you have opinions about the positive aspects or negative aspects
> of this practice, please respond.  Should it be adopted as a best practice,
> or rejected as special situation use only?
>
> Many shops probably include long sections of variable assignments, or
> perhaps globally opened files.  This is pretty much accepted everywhere as
> a good practice.
>
> In question here is the insertion of actual code - business logic or
> screen I/O programs or code snippets.
>
> Maybe you know of methods to overcome some of the obvious downsides:
> unintended 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
> else?
>
> Can the downsides be mitigated satisfactorily to justify the gains?
>
> Thanks so much.
>
> -Baker
>
>
>
>
>  ________________________________
> This communication, its contents and any file attachments transmitted with
> it are intended solely for the addressee(s) and may contain confidential
> proprietary information.
> Access by any other party without the express written permission of the
> sender is STRICTLY PROHIBITED.
> If you have received this communication in error you may not copy,
> distribute or use the contents, attachments or information in any way.
> Please destroy it and contact the sender.
> _______________________________________________
> U2-Users mailing list
> U2-Users@listserver.u2ug.org
> http://listserver.u2ug.org/mailman/listinfo/u2-users
>
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to