Re: The SAGA or is it Soap Opera Continues

As I recall, the SQL pre-compiler rules were tightened up in V5R4 and code that compiled previously may not now compile.

If you have a source member with multiple procedures, identically named local variables now must have identical definitions. That wasn't the case on V5R3.

(It has been a while since I ran into this, but I believe I have the facts substantially correct.)

Sam

Date: Fri, 30 Oct 2009 10:21:34 -0500
From: vhamberg@xxxxxxxxxxx
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] The SAGA or is it Soap Opera Continues

Frank

That's cool.

Just a thought - when you said that the precompiler insisted on unique
names across modules, might you have meant copy members? AFAIK, is
should be possible to have the same names in separate modules that are
linked into one program. I certainly hope so, as I have a need for
separate modules to handle things like case sensitive vs. case
insensitivity. You cannot set sort sequence on the fly, has to be done
at compile time, so I need separate modules for each.

Again, each module contains code only for itself and knows nothing about
another module. Hence, no conflict. Now copy members - well - you might
look at using /include instead of /copy and see what happens. Look them
up first and see what they do differently.

HTH
Vern

_________________________________________________________________
Windows 7: It helps you do more. Explore Windows 7.
http://www.microsoft.com/Windows/windows-7/default.aspx?ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_evergreen3:102009