The way I've seen this handled before was by using a preprocessor.
So instead of calling BASIC to compile your code, you have your own command
that wraps BASIC.
In your case, the first step would be to read each line, find the include
statements and insert the code (probably with * BEGIN
www.hubbardsupply.com
Delivering Products, Services and Innovative Solutions
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Daniel
McGrath
Sent: Thursday, January 26, 2012 3:31 PM
To: U2 Users List
Subject: Re: [U2
...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Dave Laansma
Sent: Thursday, January 26, 2012 2:10 PM
To: U2 Users List
Subject: Re: [U2] A Thursday Quandry...
With all due respect ... ew!
Put the DEBUG command in the INCLUDED code or make it a subroutine for the
purpose
We have used the -D and -Z2 options when compiling and it lets us see the code
from the included items when in the debugger.
-Dan
Dan Goble | IT Senior Software Engineer
Interline Brands, Inc.
804 East Gate Drive Suite 100, Mount Laurel, NJ 08054
Office: 856.533.3110 | Mobile: 609.792.6855
: Re: [U2] A Thursday Quandry...
I've ALWAYS done the -Z ... never noticed the -Z2 option -- that would read as
if it's the answer! I'll give that a try.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Dan Goble
Sent
Dan hit it on the head. I have such a pre-processor (somewhere?)
written several times over in angst when working on various
systems. David - I'll try to find it today and send it over,
then will probably post to my website.
T
From: Daniel McGrath
The way I've seen this handled before was by
