Thread: Question regarding void () in C.

Hello everyone. I'd like to get some help with this issue...

I've got a program that consists in 1 initialization of a library and 2 voids, like this:

Code:

init_library()
{
...
first(); // Once it's initialized, it takes me to the loop of void first() in which I use the program.
}
void first()
{
...
if(a=1){void second(); second();} //Example. If a=1, the code loop of void second() starts happening.
}

void second()
{
...
if(a=2){void first(); first();} //Example. If a=2, the code loop of void first() starts happening.
}

And basically it jumps from void to void all the time, which works perfectly.

My problem, however, is that in each void (first and second) I have to initialize hundreds of Bitmaps... and since I have to initialize the exact same ones both in void first and second, I thought it would be great to be able to initialize them all just once. (Also there are a lot of code lines that apply to both of the voids and that I'd like not to write them twice).

But the program is reluctant to work unless the bitmaps are declared in each void they are used. So, if you followed me up to this point, what I tried to do is to "get the 2 voids inside one void" to initialize the bitmaps in that big void, though it won't let me.

So, do you know of any way to work this out? Maybe using a .h or .rc? (tried but probably didn't link them right).

Any help is appreciated, and if you need further info, let me know. Thanks.

and since I have to initialize the exact same ones both in void first and second, I thought it would be great to be able to initialize them all just once. (Also there are a lot of code lines that apply to both of the voids and that I'd like not to write them twice).

Refactor the common code into a new static function that first and second could call. The bitmaps will have to be passed back to first and second, unless they are global bitmaps. You can pass them back by return value or by an out-going parameter if you need to.

void DoCommonThings( Bitmaps **loadme, size *arSize);

Also, call functions by their name. Anything else is not distinct enough.

Shows a pretty big lack of understanding I think. That or a big language barrier.

Hmm, probably the first option, language isn't a problem luckily.

Anyways, yes I know the basics in C, that's why I was asking how to do this. Whiteflags answer was probably right but I don't know how to apply it xD.

I've found an alternative way to solve my problem avoiding voids so thanks anyways. (Allthough if anyone is kind to give me any other solution, or explain it in more detail, I'll be checking the thread a few days more).

Originally Posted by Pecado

Hmm, probably the first option, language isn't a problem luckily.

Anyways, yes I know the basics in C, that's why I was asking how to do this. Whiteflags answer was probably right but I don't know how to apply it xD.

I've found an alternative way to solve my problem avoiding voids so thanks anyways. (Allthough if anyone is kind to give me any other solution, or explain it in more detail, I'll be checking the thread a few days more).

FWIW... they weren't talking about not using "voids"... they were talking about your rather obvious confusion about what constitutes a function...

Code:

void second()

First of all... void refers to the return value of the function you named second() ...
Secondly it's ill formed... a function that returns nothing and takes no parameters is written as

Code:

void second ( void )
  {  // stuff   
   }

Functions are good things... use them liberally! They encapsulate data and localize execution and thus provide powerful organizational tools in your programming. Basically they let you think in smaller blobs, only having to concern yourself with the immediate thing you are doing.