Then compile with respect to C99 or later, e.g., pass -std=c99 as an option to gcc.
Then compile with respect to C99 or later, e.g., pass -std=c99 as an option to gcc.
Look up a C++ Reference and learn How To Ask Questions The Smart WayOriginally Posted by Bjarne Stroustrup (2000-10-14)
well the exercise asks to compile with those particular options i said on the last comment so i can't add any other option.
Then you can use dynamic memory allocation with say, malloc and free.
Look up a C++ Reference and learn How To Ask Questions The Smart Way
No. Reread my post #16 and #18. It's broken.
Well, how about you point us to the complete assignment description, instead of giving us little tiny bits of it every 5-10 posts. The whole thing, so we know exactly what you are supposed to be doing. I suspect you aren't even really sure what the assignment is asking.
If you don't understand the problem, then you can't solve it.
If you can't solve it, then you can't program a computer to solve it.
Then please explain me where im thinking wrong thats what im asking. it works with every example you said so please explain a specific example where it doesnt, untill now i havent seen a single example where it doesnt.
in post 16 and 18 you said it was broken because the pointers could point to diferent objects, so i ask if both arrays are strings then it works because they are of the same type.
Also the second code i cant see where it's wrong, the source string can't be too big, but no word is that big to make it a problem so i think it is ok too.
these are the facts:Well, how about you point us to the complete assignment description, instead of giving us little tiny bits of it every 5-10 posts. The whole thing, so we know exactly what you are supposed to be doing. I suspect you aren't even really sure what the assignment is asking.
move n bytes from area m2 to area m1 (this function must work even if m1 and m2 share memory space).
its about strings, thats a fact and the strings can't have spaces on them, thats another fact. I know this because it is on a chapter of exercises about words that come from a wordsearch.
the exercise it's suposed to be compiled with gcc -ansi -Wall -pedantic -O2 and it must not give any warning, note, etc...
Same object and same type are not equivalent. For example, int x, y; declares two ints. They are both the same type, but are not the same actual object. Similarly
foo and bar are not the same object. If you pass them to your function and try to subtract them, it results in undefined behavior. Undefined behavior is bad. Read these two links:Code:char foo[100]; char bar[100];
Question 11.33
LLVM Project Blog: What Every C Programmer Should Know About Undefined Behavior #1/3
Just because it seems to work doesn't mean it's a good idea. You're simply getting lucky.
We're telling you that it is wrong. If you don't want to listen to us because it doesn't look wrong to you (even though you are a novice), then why even come here asking for help? And for the last bloody time, you need to test thoroughly. You should try to break your function. If you can't in any way break it, and it meets all the requirements, then you were successful. If you don't believe me that it's broken, try this:
Does the output look right to you?Code:char foo[10] = "short"; char bar[40] = "supercalifragilisticexpialidocious"; movefunction(foo, bar, 100); // feel free to try a shorter number like 20 printf("foo = %s\n", foo); printf("bar = %s\n", bar);
