I'd agree but I'd also add that I think part of the ickyness is from
using SEU...

With SEU, /copy "hides" stuff from you; to see it, you've got to open
the /copy member in another SEU session...

Whereas with WDSC, the stuff defined in the /copy member shows up in
the outline view just like locally defined stuff. And it just takes a
simply right click to browse the actual /copy member.

Charles

On Thu, Jun 30, 2011 at 5:59 PM, Barbara Morris <bmorris@xxxxxxxxxx> wrote:
On 2011/6/29 10:11 PM, John Yeung wrote:
...  I've always gotten
an icky feeling with /copy, but I suppose it's no worse than
#include-ing C header files.  (Not that I'm too happy with #include.)
It's yet another place where the program is scattered about, another
piece to maintain.  We'll see how it goes.


I've heard others have icky feelings about /copy, and I think it usually
stems from disliking the practice of copying in calculations.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.