>I can't see any other way to pass the ... arguments, other than
>through the "va_list args" and va_start lines, am I wrong in thinking that
Nope, you're right on track.

>Can someone explain me what does this mean?
>"40[^\"], %*c"
Assuming it's actually "%40[^\"], %*c", it means read a string of up to 40 characters or until a double quote is found (%40[^\"]), then...

>Now the question is how the Assember was implemented, i mean which language?
Any compiler can be written in a suitable existing language. The first assembler was probably hand compiled as machine...

>new_node->first->next = my_list->first;
my_list is a type, not an object. Perhaps you meant:

new_node->first->next = my_this->first;

Your code is C++, not C. In C++ void* conversions are not implicit and require a cast.

>lets say m=2, n=2 => calls m=1, n=1 => m=0,n=0 which returns num_elements =0
>control comes to fn m=1, n=1, num_elements get incremented and returned.
>control comes to m=2, n=2, num_elements get...

No code, no help. Read our rules.

Five days, huh? Maybe you aren't cut out for programming? Post your code and somebody will try to help you.

>but still compiled and ran without incident..
Yet another ding against gcc for not conforming to the standard, I suppose. Those switches put the compiler in strict conformance mode, which means a...

>I tried compiling this with the GCC compiler and its works...
Try again with the -ansi, -pedantic, and -Wall switches.

>whats the story.
The story is that the code you posted is not valid C. You're likely relying on a compiler extension that allows nested function definitions. What compiler are you using?

>i understand recursion, [but my] basic doubt is <blah blah>
That doubt is precisely why I don't believe you understand recursion. So why don't you explain how recursion works to me, using a common...

>but many books have this specifier.
I hate to break it to you, but many books are written by people who know little more about C than you do. The lesson about %lf is that printf is not a mirror...

If you don't understand recursion, trace through the execution and see exactly what happens:

#include <stdio.h>

int function ( int m, int n )
{
int num_elements = 0;

printf ( "Entering...

>If you expect your IDE to come fully featured then it won't be lightweight....
The very definition of IDE implies a text editor, a compiler, a debugger, and build tools. vim is a text editor, not...

Q: Do you know how to do it on paper?
(a) No: Go figure that out before trying to write code.
(b) Yes: Show us your code, and be more freaking specific about what problem you're having.

Since...

>it won't work the way i want it
So fix it. We're not the psychic friends network, here to solve all of you problems with a crystal ball and smile. You wrote the damn program (and it's very short!),...

>i read that the precision of float is 6 digits and double is 10.
No, the precision of float is FLT_DIG and double is DBL_DIG, where both of those macros are defined in <float.h>.

>but it is...

>num_elements is returned by each call recursively, will it be
>overwritten with the local variable , from the calling function ?
num_elements is returned, but never modified except to increment...

>Is there any suggestion for improvement
Yes, I can recommend improvements:

>scanf("%d",&n);
Always check your input functions for success. Especially with user input, and more especially with...

In your current code you declare num_elements both in the global scope, and locally within main. When multiple variables from different scopes have the same identifier, the one from the most local...

That makes more sense. In the future it would be nice to include those defines in the code, if only to make life easier for the people helping you.

Anyway, your algorithm is somewhat nonsensical....

>The serial number of motherboard must be obtained.
>How to do it under Windows ?
WMI FAQ (http://technet.microsoft.com/en-us/library/ee692772.aspx).

>Actually it does compile.
TYPE is never defined, which causes a relatively large number of errors regardless of which compiler one uses. You also rely on non-portable behavior that breaks two of...

>The better method as per me is
You do realize that the same solution was suggested in this thread three years ago, yes? :icon_rolleyes:

inline: Similar to C++'s inline keyword. It gives you the option of telling the compiler that you want inline expansion rather than real function object code. Inline functions are a safer and easier...

>the compiler is actually giving an error though -- "invalid operands to binary *"
The compiler is actually right. Multiplication for pointers is nonsensical. Why don't you tell us what you're...

>And here int edadMedia(struct persona * nombres) { }
>i wanted to create a pointer to an array of structs
That close to what you said, and personally I think it's what you really meant. When you...

>Because the OP created the arrays without a size.
And without a type. Are we also to assume that he wants a variant type?

>You're the first one in this thread to be rude.
If you think that's...

>With two dynamic arrays, your structure needs pointers to the arrays.
You're the first one in this thread to mention dynamic arrays. Why over-engineer the problem and confuse the OP?

>array1[];
>array2[];
A type and a size are both required.

>length;
A type is required.

>name1.array1[4] = {3,0,7};
>name1.array2[4] = {0,15,0,-4};
Alas, arrays can't be assigned to like...

Use nombres the same way in edadMedia as you did in main (ie. as an array). However, I strongly recommend that you pass the size of the array as well so that you can avoid bogus indexes in edadMedia....

If you know how to use arrays, and you know how to use FILE pointers, you know how to use arrays of FILE pointers. There's really nothing tricky about it except for the number of files you can have...

>I don't really see your point....
That much is obvious.

>Is your point that is not 100% the standard?
My point is that it could potentially be the cause of your problem because a compiler is...

>Maybe I'm having problems with this statement
>"the result shall compare equal to the original pointer"
It means that you can convert an object pointer to or from a void pointer without any loss...

>Could you give an example....
Your code is an example, my fix for your code is a counter-example. What more do you want? How about a quote from the standard:

The key terms here are incomplete...

>No the complier had no problems casting a void pointer to a function..should it?
It might. Technically void* and functions pointers are incompatible and converting between them is undefined...

C doesn't specify tab stops, only tab characters. It's up to the program consuming those characters to interpret the character with a certain tab stop length, just like it's up to the same program to...

>i spent lot of time in googling but couldnot get it.
Hmm, perhaps that's because it's copyrighted and any free PDF you find is illegal? If you want the book that badly, go buy it. If you can't...

>Please help me find the mistake!
I suspect the mistake is a complete failure to study whatever book on C you have. Instead of trying to finish this exercise in one swell foop, perhaps you should be...