MIDRANGE-L » February 2013

Re: cl compile severity level

Subject: Re: cl compile severity level
From: Mark S Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>
Date: Wed, 20 Feb 2013 11:22:04 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Hi, Rob:

Aha, now I understand. In that case, using &named variables for those "constants" is probably the way to go. :-)

Mark

> On 2/20/2013 11:14 AM, rob@xxxxxxxxx wrote:

No, they won't fail at run time. Because at run time the compiled object
will be on the right system.

Rob Berendt

This thread ...

RE: cl compile severity level, (continued)
- Re: cl compile severity level , rob

References:
- cl compile severity level , rob
- RE: cl compile severity level , Paul Therrien
- RE: cl compile severity level , rob
- RE: cl compile severity level , rob
- Re: cl compile severity level , Mark S Waterbury
- Re: cl compile severity level , rob

Prev by Author: Re: How to Find what module a procedure is located in
Next by Author: Re: how to kill all jobs that have a lock on a file
Previous by thread: Re: cl compile severity level
Next by thread: RE: cl compile severity level
Index(es):

Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact