lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev lynx2.8.2dev.18


From: pg
Subject: Re: lynx-dev lynx2.8.2dev.18
Date: Thu, 4 Mar 1999 12:17:18 -0700 (MST)

In a recent note, Kim DeVaughn said:

> Date: Thu, 4 Mar 1999 09:11:50 -0800
> 
> On Thu, Mar 04, 1999, address@hidden (address@hidden) said:
> | * change the LYK_xxx keymap definitions to an enum, to simplify ifdef's - TD
> 
> THANK YOU, Tom !!!
> 
Just curious, as a novice C programmer: In what way does an enum simplify
ifdef's?  I presume this is enum a/a several #define's.  Can't you just
pick one of the defined macro names and use it in any necessary ifdef?

Are there any portability concerns with enums?  Harbison and Steele
says, "not all compilers implement enumerations, and those that do
are not consistent in their implementations."

I haven't compiled dev.18 on OS/390 yet.  I know that on OS/390,
enums are a serious portability obstacle: while OS/390 is perfectly
ANSI compliant as I read the standard, it defies general expectations
regarding the representation of enums in storage.  If a procedure
has a formal parameter of type (enum *), you may not be able to pass
it an (int *), for example.

-- gil

reply via email to

[Prev in Thread] Current Thread [Next in Thread]