On 18/11/2014 1:07 PM, Paul Gilmartin wrote:
On Mon, 17 Nov 2014 17:55:10 -0800, Charles Mills wrote:
Bingo! Thanks.
IIRC, the SAS/C compiler put them inline if declared "const";
in WSA otherwise. I believe it does not violate ANSI C if an
object is declared "const" in one translation unit, with "const"
omitted in another, as long as it is not modified by the former.
Of course, this caused chaos with SAS/C.
Hmm, and that's the problem with ANSI C (and C++). The standards can be
interpreted in different ways which leads to inconsistent
implementations. Throw into the mix the likes of Microsoft compilers
violating the
standard and you have the problem we have today with portability issues.
IMO, static const should be inlined like C++ does but certainly not
extern variables.
(BTDT)
-----Original Message-----
From: David Crayford
Sent: Monday, November 17, 2014 5:38 PM
The compiler wants to put all external variables into WSA. To turn that off
specify norent.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
