Printable View
Hello everybody,
I am learning C language and I would like to make some quiz to test my progress. I have taken the test on BrainB and TechniProfiles site but they have little question. Who know another link that have the good quiz, please help me.
Thanks for your kindness.
Trancongan.
Is this correct?
Which one is correct:Code:while ( p != NULL ) {
free( p );
p = p->next
}
orCode:char *p
strcpy( p, "hellow world." );
Code:char *p = "hello";
Prelude's semi-difficult quiz for people wanting more than hello world questions.
---------------------------------------------------
1) How many ways according to the C standard can main be defined?
2) What will the following code print?
3) What does the following declaration mean?Code:char *p = "World";
printf ( "%*c%p %p!\n", 18, ' ', "Hello, ", p );
typedef struct foo { int foo; } foo;
4) (True or False): An int is 4 bytes.
4b) An int is 4 times the size of a char.
5) (True or False): a[x] = ++x; is valid.
5b) is safe.
6) What is wrong with the following code:
7) (True or False): Mergesort partitions a file and then recursively sorts each part.Code:struct s { int foo; } one = {1}, two = {2};
one.foo ^= two.foo ^= one.foo ^= two.foo;
printf ( "%d %d\n", one, two );
8) Is the following code valid C?
9) What will the following code print:Code:#include <stdio.h>
int main ( void )
{
int i;int i = 5;int i;
printf ("%d\n", i );
return 0;
}
9b) What if the printf were changed toCode:char *p = malloc ( 20 * sizeof *p );
printf ( "%u\n", sizeof p );
printf ( "%d\n", sizeof *p );
10) Assuming a is a working array, is the following code valid?
1[a] = 1;
Please don't run the programs or test the code, this is a quiz on your knowledge of C, not running test programs.
-Prelude
.no . you could assign p then free, but its pointless.Quote:
Originally posted by Nutshell
Is this correct?
Code:while ( p != NULL ) {
free( p );
p = p->next
}
I'm going with the second. The first is is going to get you a pointer intialized to the more-or-less random contents of the stack locationQuote:
Which one is correct:
orCode:char *p
strcpy( p, "hellow world." );
Code:char *p = "hello";
1) I'm thinking int main(void), int main(), and
int main(declarations).
2) I'm not sure.. can, is *p a generic *s?
3) it is the equivalent of int struct;
4)
a) false (maybe on an ancient RISC arch)
b) false
5)
a) I don't think so.
b) I hope not.
6) It is completly screwed up. you missed the semicolon after the struct, and your calling it members all wrong.
7) False, you never said anything about merging the sorted sublist into a single sorted list at the end. Oh yea the partitions are equal unlike quicksort and if my memory is serves me, your looking at O(nlog(n)).
8) No you can't redeclare.
9) Can you even do that??
10) I'm just guessing... yes.
Have you tried the 1 on this site?
http://www.cprogramming.com/cgi-bin/quiz.cgi
Can't be seen as wrong. :D
>The first is is going to get you a pointer intialized to the more-or-
>less random contents of the stack location
Actually, it should result in a run-time error because you are assigning to memory that you don't own.
Three. int main ( void ), int main ( int argc, char **argv ), int main ( int argc, char *argv[] ). Those three are stated explicitly but it does say that any names for argc and argv can be used.Quote:
1) I'm thinking int main(void), int main(), and
int main(declarations).
It will print 18 spaces, an address, a space, and then another address.Quote:
2) I'm not sure.. can, is *p a generic *s?
Could you elaborate?Quote:
3) it is the equivalent of int struct;
The actual sizes of integers will vary from system to system, so both are false.Quote:
4)
a) false (maybe on an ancient RISC arch)
b) false
It is valid, but is most definitely not safe. Though quite a few compilers will flag a warning, I don't think any will halt compilation.Quote:
5)
a) I don't think so.
b) I hope not.
I didn't miss the semicolon, it was placed after declaring and initializing the instances. The printf may or may not work, and the swap operation is absolutely hideous. The swap is also undefined, care to guess why?Quote:
6) It is completly screwed up. you missed the semicolon after the struct, and your calling it members all wrong.
Correct, I was describing Quicksort, not Mergesort. :)Quote:
7) False, you never said anything about merging the sorted sublist into a single sorted list at the end. Oh yea the partitions are equal unlike quicksort and if my memory is serves me, your looking at O(nlog(n)).
Nope, it's completely valid as long as only one of the variables is initialized. If any more are initialized then it constitutes a redeclaration and the compiler will flag an error. But as is that code will compile and work.Quote:
8) No you can't redeclare.
Absolutely, it won't give you the results you want, but it will most certainly work. The first print will result in the size of a single pointer and the second will result in the size of a single char.Quote:
9) Can you even do that??
Good guess, if you break down array notation to pointer notation you have *( 1 + a ) = 1, which is perfectly valid.Quote:
10) I'm just guessing... yes.
-Prelude