Thread: problem with a function

Hi there

I've come to a point where i need to do something like this that is i won't know how many parameters the user would pass. Take a look at the function below:

Code:

int myfunction(char buf, int no, const mystruct s1,...);

umm i need to capture all the structs the user passes in an array... 'no' will be holding the number of structs passed.... Working with arrays i know a bit, however i have never yet worked with these type of functions.... Can some1 help me on this pls?

Don't over complicate things unnecessarily:

Code:

int myfunction(char buf, int no, const mystruct* sArray);

to access all the structures, simply write:

Code:

int i;
for (i = 0; i < no; i++)
{
//something with sArray[i];
}

thx.. yeah i know about that way... however i have the "complicate" things as its the only way the end user will communicate through the function, I can't force him to pass the function an array...

Originally Posted by MacGyver

I'm not sure how you can make sure the "end user" pass each argument individually any more than you could make him do it as an array.

Not to mention it makes it impossible to call the function when you don't already know how many structures you need to pass. Variadic functions are usually the worst choice for such things.

its because i got a structure for a task i'm doing and i must follow, as for the array part i already did it, however i'm now trying to collect them individually, put them in an array and pass the array to the function i already implemented which is working fine...

However i never worked with variadic function or what they're called... i didn't even know they were called like that before... Anyway i guess thanks all the same :s

Here's an example using variable arguments, I've written not so long ago.

Originally Posted by MacGyver

I'd much rather have printf() in that form rather than having to build an array of void *'s everytime I want to call it.

So would I, but in the case of printf(), you always know how many arguments you will be passing, because that number is strictly dictated by the conversion specifiers. In the case of a function which processes a bunch of structures in some way, you may not know how many structures need processing until runtime.