Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!charyb!dan
From: dan@kfw.COM (Dan Mick)
Newsgroups: comp.lang.c
Subject: Re: Prototypes for macros?
Message-ID: <1990May8.031743.7921@kfw.COM>
Date: 8 May 90 03:17:43 GMT
References: <1990May3.202403.10140@laguna.ccsf.caltech.edu> <1990May4.033226.630@kfw.COM> <1990May4.162637.29981@laguna.ccsf.caltech.edu>
Reply-To: dan@kfw.com (Dan Mick)
Distribution: comp
Organization: KFW Corporation, Newbury Park, CA
Lines: 31

In article <1990May4.162637.29981@laguna.ccsf.caltech.edu> gleeper@tybalt.caltech.edu (Evan Manning) writes:
>I guess I should have mentioned that I'm not a rank amateur.  

That, or not been so frigging touchy.  Sheesh.

>All
>appropriate headers were included (including time.h for seeding off
>the time in randomize()) and these are the precise same headers needed
>to avoid warnings after manually expanding macros.  My guess is that
>Turbo is checking for prototypes *before* expanding macros.  Which
>sounds wrong to me.  Has anybody encountered this before?

Well, tell ya what, Evan:  Try this test case.  It gives no warnings or
errors under TC 2.0 for me:


#include <stdlib.h>
#include <time.h>

int main(void)
{
    randomize();
    return 0;
}

Now what happens?  

BTW, for some more rank amateur suggestions that just might help, since
the problem you're having is most likely not the compiler....did you
try to reduce it to a small test case?  Did you look at stdlib.h for any
enclosing ifdefs that might rule out the prototypes you want?