[lwip-devel] [bug #20478] memp_malloc returns bogus value on malloc failure

[Jared Grubb]

Follow-up Comment #5, bug #20478 (project lwip):

Another way of thinking about it: When creating the linked list, we are
pushing new elements onto the *front* of list, like a stack. So, the first
element processed gets next=NULL, but it is still the _last_ one in the list
(stacks are FILO).

This may seem backwards, but it can keep you from having some weird behavior
in threaded environments.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?20478>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/