Ethereal-dev: RE: [ethereal-dev] c code in ncp2222.h

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Graham Bloice" <graham.bloice@xxxxxxxxxxxxx>
Date: Fri, 22 Sep 2000 16:50:49 +0100
> What do you think? Which is cleaner?
> 
> 1. Moving the C code into a separate compilation unit and making
> all the data tables in the generated C non-static.
> 
> 2. Keeping the symbols static by using #included source code and
> putting in a comment to better explain this hack?

How about putting the source code into another *.c file and #include that ?

I believe that there is something similar in GTK/Glib

> 
> 3. Moving the C code into the python script as strings and putting it
> in the generated C file.
> 
> If people want it another way (that is, other than the current
> way, which is #2), I'll change it. In the end it matters little to me.
> 
> --gilbert
> 


Regards,

Graham Bloice