× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.