The following function is used to get some data from an external source (whatever is this source) and store them into the provided buffer.
int GetData(unsigned char* aBuffer);
Why is this function “dangerous”? How would you improve it so that it is not dangerous? (Hint: the question is not about the return value or the details of how the data is received).
buffer overrun
add buffer length as a parameter
All problems in computer science can be solved by another level of indirection,
except for the problem of too many layers of indirection.
– David J. Wheeler
thanx for that
another question , is the following sytax correct ?
typedef int myfunc(void*) myDefinedFunc();
I don't think so...
this syntax resembles some definition of the pointer to the function, but where is the * indication that?
And you cannot define type "function" only "pointer to function" is possible
All problems in computer science can be solved by another level of indirection,
except for the problem of too many layers of indirection.
– David J. Wheeler
> another question , is the following sytax correct ?
> typedef int myfunc(void*) myDefinedFunc();
Type it into a C program and compile it to find out.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
