What are the pros/cons of using Callback mechanism in C? (Design perspective)

What are the scenarios where it can be applied ?

Tuxpal

In 'comp.lang.c', sureshjayaram@rediffmail.com (Tuxpal) wrote:

> What are the pros/cons of using Callback mechanism in C? (Design
> perspective) 

pros : flexibility, reusability, modularity, testability.
cons : the produced code can be harder to read or to debug... specially when 
several levels of callbacks are implied.
 
> What are the scenarios where it can be applied ?

Mainly, software components (flexible libraries). Actually, it covers any 
kind of applications... Sky is the limit.

-- 
-ed- get my email here: http://marreduspam.com/ad672570
The C-language FAQ: http://www.eskimo.com/~scs/C-faq/top.html
C-reference: http://www.dinkumware.com/manuals/reader.aspx?lib=c99
FAQ de f.c.l.c : http://www.isty-info.uvsq.fr/~rumeau/fclc/

In <59cd9c4d.0406240337.665ad4c8@posting.google.com> sureshjayaram@rediffmail.com (Tuxpal) writes:

>What are the pros/cons of using Callback mechanism in C? (Design perspective)

It's a design issue, not a language isse.

>What are the scenarios where it can be applied ?

For starters, have a look at the specification of bsearch() and qsort()
from the standard C library.

Dan
-- 
Dan Pop
DESY Zeuthen, RZ group
Email: Dan.Pop@ifh.de

"Tuxpal" <sureshjayaram@rediffmail.com> wrote in message
>
> What are the pros/cons of using Callback mechanism in C?
> (Design perspective)
>
> What are the scenarios where it can be applied ?
>
Callbacks are usually used to leave some functionality out of a module, to
be provided by the caller. A standard library example is qsort(). Another
example would be if you implement some sort of database structure, and
require the caller to provide a getkey() function to retrieve the key from
the data.

The advantage is that the functions using callback are much more general.
qsort() for instance can sort any flat array without being recompiled.

One disadvantage is that providing the callback puts quite a burden on the
caller - you have to know exactly what the comparison function provided to
qsort() is expected to return, for example. If you accidentally return
order-dependent results for two items that in fact compare as equal then the
call could strangely fail just before shipping.

Another disadvantage is that it is harder to write a call-tree of a program
that uses function pointers. For short callbacks this isn't too much of a
problem, but if you use them too heavily you can no longer have a structured
program. This can be a difficulty in Windows programming, for example.