Answer Posted / sujith

I would like to answer this question from a compiler
perspective. When we have if else or if else tree, we have
many compare instructions ( assembly generated by compiler)
where as switch has only one compare and jump instruction.
If the idea is to does something after comparing the values,
it is always better to go with the switch case than if else
tree.

I would appreciate analyzing the assembly code, with the
same source, with if else tree and switch case statements.

What is the process of writing the null pointer?

995

---

What is the scope of static variable in c?

964

---

How does selection sort work in c?

999

---

Can we change the value of static variable in c?

986

---

How can I call fortran?

1000

---

How can I write data files which can be read on other machines with different word size, byte order, or floating point formats?

985

---

Explain what is the heap?

1025

---

my project name is adulteration of chille powder.how can i explain it to the hr when he asks me about the project?

1546

---

string reverse using recursion

2395

---

What does the file stdio.h contain?

1015

---

Why is not a pointer null after calling free? How unsafe is it to use (assign, compare) a pointer value after it is been freed?

1066

---

Difference between strcpy() and memcpy() function?

1088

---

Why is c so popular?

1124

---

How to set file pointer to beginning c?

1168

---

What is the use of clrscr?

1068

---