Microdata dropped the ball on the INCLUDE 20 years ago which offers this
solution that I use for all of my MCD clients today. Here's the source
snippet
***
* PROGRAM NAME
* MARK JOHNSON 020205
***
GOSUB GET.INCLUDES
OPEN "CUSTOMER" ETC
<snip everything else>
GET.INCLUDES:*
INCLUDE THING1
INCLUDE THING2
INCLUDE THING3
RETURN
END (of source code)
Since MCD doesn't allow RUN and external SUBROUTINE programs to intermingle,
I write my handy subs from other clients as INCLUDES and include them at the
end. Just be careful of an imbedded RETURN on THING2 above preventing THING3
from executing.
My 1 cent.
----- Original Message -----
From: "Mike Farrant" <[EMAIL PROTECTED]>
To: <u2-users@listserver.u2ug.org>
Sent: Wednesday, February 02, 2005 9:58 AM
Subject: [U2] [UV] RAID debugger
> Talking of debuggers, can anyone remind me how the $INCLUDE s can mess
> up the line numbers displayed within the RAID debugger.
>
> I had a solution to this once which I seem to remember had something to
> do with the configuration or placement of the $INCLUDE lines in the
> source code.
>
> I look forward to any response
>
> Thanks
>
> Mike Farrant
> -------
> 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/
