It is currently Tue, 30 Nov 2021 17:38:53 GMT



 
Author Message
 gcc #define #define #define

Simple. There are several standards designed to alleviate
porting pains. ANSI C, POSIX, X/Open are the major ones.
As long as your program adheres to the above standards it
is easily portable. E.g. for most Xlib and/or Motif programs
it is only required that you need a different makefile
because of various include and lib directories. In fact,
Linux is one of platforms that provide both BSD and SysV
library calls and other features. Try to write or port
something to/from SunOS to IRIX then you will see what all
those #ifdefs are all about. :)

Let me find an example to back up my point: I write a
program and I need to find a way to zero out a memory
area. I found several library functions that can do that,
bzero() and memset(). I look at the bottom of the man
pages:

bzero() CONFORMING TO BSD 4.3

memset() CONFORMING TO SVID 3, BSD 4.3, ISO 9899

Now it is obvious that it is better to use the latter.

Unless, of course, I misunderstood you. What exactly are
you dealing with where you have problems with lots of #ifdefs?
Then maybe me or someone else can provide you some more
specific assistance?

--
<vladimip at uniserve com> | Good pings come in small packets
     Vancouver, BC | SIGSIG: signature too long (core dumped)
Things are more like they are today than they ever were before -
(From a crosspost between alt.suicide and alt.destroy.microsoft)



 Mon, 21 Feb 2000 03:00:00 GMT   
 gcc #define #define #define

So just write C++ - if you are fine with C, you can just write =

procedural (non-OO) C++, and you get rid of almost all '#defines'.

Ok, conditional compiling is still needed, ...

Jochen

-----------------------------------------------------------------------
  Jochen K=FCpper

  Heinrich-Heine-Universit=E4t D=FCsseldorf     joc...@uni-duesseldorf.de=

  Institut f=FCr Physikalische Chemie I
  Universit=E4tsstrasse 1, Geb 26.43.02.19       phone ++49-211-8113681
  40225 D=FCsseldorf                             fax   ++49-211-8115195
  Germany             http://www-public.rz.uni-duesseldorf.de/~jochen
-----------------------------------------------------------------------



 Tue, 22 Feb 2000 03:00:00 GMT   
 gcc #define #define #define

_Absolutely_ DISagree (no flame intended either).  Maybe it's
just a personal quirk, but I find DEGREES_TO_RADIANS much more
understandable than 57.29577.



 Thu, 24 Feb 2000 03:00:00 GMT   
 
   [ 3 post ] 

Similar Threads

1. m4: how to define var if another defined

2. #define _POSIX_C_SOURCE and other defines

3. gcc not defining _start, ld not linking correctly

4. Platform-specific preprocessor symbols automatically defined by gcc

5. GCC gives error on any math.h defined functions


 
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by ST Software