[ofa-general] [PATCH] Allow paths to the device specific library to be absolute

[Jason Gunthorpe]

On Thu, Jul 23, 2009 at 02:17:17PM -0700, Roland Dreier wrote:
> 
>  > > I don't have a debian logon, but I do have an ia64 machine:
> 
>  > Ah, in the good old days every DD had one of those :)
> 
> BTW I'm not a dd -- just have a sponsor for my packages.
> Maybe someday I'll try to become a dd but for now I'm too lazy.

Ah! Yes, that all changed some years ago. I got my DD-ship over an
IRC conversation, these days you have to jump through hoops!
Unfortunately I haven't used it in 8 years and the password is lost
to me.

>  >  The identifiers in an enumerator list are declared as constants that
>  >  have type int and may appear wherever such are permitted.
>  > 
>  >  Each enumerated type shall be compatible with an integer type. The
>  >  choice of type is implementation-defined, but shall be capable of
>  >  representing the values of all the members of the enumeration.
> 
> thinking about this, I confused myself.  Given
> 
> enum foo { FOO, BAR };
> 
> and given that the standard quoted above says FOO and BAR have type int,
> why is it valid to do

Well, this is messy.

C++ and C are different. C++ strongly considers the enum constant to
be of the enum type, and implicit casting from int to enum is not
allowed.

In C99 this is only weakly true (due to the legacy), and it is up to
the compiler to optionally produce a warning if arbitary ints are cast
to the enum (the other text I quoted from Annex I, Common Warnings)

Jason