Hi,

I just inherited a substantial number of source files with this in
them:
#ifdef _WIN32
Sleep(2000);
#else
sleep(2);
#endif

Being new to C, I'm trying to figure out if this can be consolidated
into a simple macro instead of peppering this all over the place.
Anyone have any examples?

TIA,
-T

On Jun 8, 10:33 am, "Douglas A. Gwyn" null.net> wrote:

actually, i think not. this is a compiler issue when an implicit type
conversion (between different flavors of int) *may* cause a change of
value. when building a big project, if you want to impose a
discipline on a bunch of different programmers to not do sloppy
actions that might loose bits somewhere where you won't be looking
(because it is not apparent that any such values were changed in an
expressed equality), these *potential* problems should be flagged in
the build. then you can go into the code, examine it, and if you
think the conversion is kosher, put an explicit cast on it. then the
warning goes away.

presently using linux gcc:

$ gcc -v
Using built-in specs.
Target: i386-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --
infodir=/usr/share/info --enable-shared --enable-threads=posix --
enable-checking=release --with-system-zlib --enable-__cxa_atexit --
disable-libunwind-exceptions --enable-libgcj-multifile --enable-
languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --
disable-dssi --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre
--with-cpu=generic --host=i386-redhat-linux
Thread model: posix
gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)

i run it on this program:
FILE: hello.c

//
// $ gcc -Wconversion -o hello hello.c
// $ hello
//

I would just like to say thank you to both of you for your comments on
my code and for the answers to my questions. I will be rewriting the
code to be more robust and adding a few features. After I finish I
will be reposting so hopefully some other people can learn like I have
from this program and your posts.
-Thankyou