|
Simon,
As Raul pointed out, the trouble with putting it into a service program is
that then the message is sent from the service program rather than from the
program - not much help when trying to track down error messages etc. That
was one of his main points!
Rory
On Wed, Apr 28, 2010 at 4:29 PM, Simon Coulter <shc@xxxxxxxxxxxxxxxxx>wrote:
On 29/04/2010, at 8:59 AM, Rory Hewitt wrote:
2. Include MSG as a copy member *twice* in the main source member -
once at
the top, with the other D-specs, and once at the very bottom, like
this:
Arrgh! Surely duplicated code such as this is crying out for inclusion
in a service program instead of being copied (like old RPG II) into
every program that requires it? Might as well be binding to the same
module in every program.
Regards,
Simon Coulter.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
