[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #62832] Allow NULL buffer to pbuf_get_contiguous()
From: |
Colin Foster |
Subject: |
[lwip-devel] [bug #62832] Allow NULL buffer to pbuf_get_contiguous() |
Date: |
Mon, 22 Aug 2022 11:24:14 -0400 (EDT) |
Follow-up Comment #2, bug #62832 (project lwip):
[comment #1 comment #1:]
> When the required data spans more than one pbuf, null is passed in and the
data cannot be copied out
That's the point I address below. If data spans more than one pbuf, NULL would
be returned in which case further action (allocating a buffer on the stack,
for example) would become necessary. But in cases where the payloads almost
never (or actually never) span multiple pbufs, why force the user to always
allocate a separate buffer that'll never get used?
_______________________________________________________
Reply to this item at:
<https://savannah.nongnu.org/bugs/?62832>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/