Operating System
01/26/2007 09:14 AM
Please respond to The IBM z/VM Operating System
From
Dave Jones <[EMAIL PROTECTED]>
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: Fw: a C language question
Thanks for the information, Mike. I appreciate it. Using the target
value you suggest
<[EMAIL PROTECTED] Subject
ARK.EDU> Re: Fw: a C language question
Subject
ARK.EDU> Re: Fw: a C language question
01/25/2007 12:09
John, it turns out that using the #define _NONEW_FUNC_CHECK doe not
simply revert to the default of having the undeclared getaddrinfo
function return an int. It actually generates the following:
#pragma map (getaddrinfo, "@@GTADRI")
#pragma map (getnameinfo, "@@GTNAM
Well, John, I did say it didn't give me the warm fuzzes.:-) It does
appear that my default TARGET compile value is (LE, CURRENT), but that
doesn't work without the #define _NO_NEW_FUNC_CHECK.
Here's a list of all the compiler options in effect at compile time:
'GETADDRI C A1'
*NOGONUMBE
Dave,
In a word: Not a good idea.
That define means that the declaration of the offending function is
omitted and you fall back on the default of all undeclared functions
being something returning int, but that suppresses type checking of
the function arguments.
You need to convince the compil
Thanks to the help and advice of the good folks on this list, I have
managed to solve my C compiler problem. Turns out that I need to do a
#define _NO_NEW_FUNC_CHECK
at the beginning of the code. That tells the C compler (C/C++ for z/VM,
btw) to actually include the correct code to invoked the
