🚀 go-pugleaf

In article <4jbciv$2kk@solutions.solon.com> vjarnot@mnw.net "Asmodeus" writes:

>
>I have set up an array in the following manner (obviously I just need
>0 or 1) :
>
>typedef struct my_bits {
>        unsigned the_bit : 1;
>};

I assume you meant:

typedef struct {
        unsigned the_bit : 1;
} my_bits;

The first problem here is that the struct does *not* consist of just one bit.
The smallest size it can have is 1 byte (char) and it could well be more
depending on how your compiler allocates bitfields.

>my_bits the_array[800][800];
>
>        My question is this : I have read that some operations ( =,+,- are
>what I use) are slower when performed on bits as opposed to other
>types.

On most archetectures, yes.

> My objective is to optimize the code for speed, and I figured
>using less memory would help me do so, now I'm having doubts.  So what
>is more efficient, bits or some other type???

Unless you ave platform specific information to the contrary you should
assume that int/unsigned int are the most efficient integer types.

-- 
-----------------------------------------
Lawrence Kirby | fred@genesis.demon.co.uk
Wilts, England | 70734.126@compuserve.com
-----------------------------------------