scope of malloc

[Oliver Laumann]

In article <14437 at smoke.brl.mil> gwyn at smoke.brl.mil (Doug Gwyn) writes:
> In article <2182 at kraftbus.opal.cs.tu-berlin.de> net at tubopal.UUCP (Oliver Laumann) writes:
> >You also keep mentioning the argument that alloca() is not needed.  If
> >this is true, then how do you make sure that in the following function, ...
> 
> I don't write spaghetti code.

I'm not sure I understand this remark.  According to the computer jargon
dictionary, spaghetti code is defined as follows:

SPAGHETTI CODE (sp at -get'ee kohd) n. Describes code with a complex and
   tangled control structure, esp. one using many GOTOs, exceptions or
   other `unstructured' branching constructs. Pejorative.

In what way did the program fragment in my article qualify as spaghetti
code?  Do you regard "callback functions" as a tangled control structure
or an unstructured branching construct (in this case you must really
hate X11 :-)

--
Oliver Laumann     net at TUB.BITNET     net at tub.cs.tu-berlin.de     net at tub.UUCP