Re: Avoiding #ifdefs

CoDeBrEaKeR <[email protected]>
Newsgroups gmane.linux.ports.arm.general
Message-ID <[email protected]>
Thanks,

 But the stucture am using is pretty insanely nested.

~A

--- On Wed, 1/6/10, Marek Vasut <[email protected]> wrote:

> From: Marek Vasut <[email protected]>
> Subject: Re: Avoiding #ifdefs
> To: [email protected]
> Cc: "CoDeBrEaKeR" <[email protected]>
> Date: Wednesday, January 6, 2010, 11:53 AM
> Dne St 6. ledna 2010 07:04:37
> CoDeBrEaKeR napsal(a):
> > Most of the times its is easy to start having a lot of
> #ifdef statements in
> >  your code. Since this is not a proper thing to
> do, placing the #ifdef in a
> >  header file would be the usual suggestion. well,
> i understand this as far
> >  as #ifdefs in functions are concerned. How about
> structures?
> > 
> > for Ex:
> > 
> >  static struct something = {
> >     .name       
>            = "xyz",
> >     .driver_name     
>       = "something",
> > #ifdef SOME_ARCH_TYPE
> >     .bla       
>             = DO_THIS,
> > #else
> >     .bla       
>             =
> DO_SOMETHING_ELSE,
> > #endif
> > };
> > 
> > How do i avoid #ifdef here, any idea??
> 
> If you want to do some run-time detection, then do so and
> assign 'bla' at 
> runtime...
> if (x)
>  something.bla = somefn;
> else
> ...
> > 
> > Thanks.
> > 
> > ~A
> > 
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > linux-arm mailing list
> > [email protected]
> > http://lists.infradead.org/mailman/listinfo/linux-arm
> > 
> 
> _______________________________________________
> linux-arm mailing list
> [email protected]
> http://lists.infradead.org/mailman/listinfo/linux-arm
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.