Re: [lwip-devel] Extended udp_recv callback

[Jonathan Larmour]

Kieran Mansley wrote:
> 
> I think a combination of the two approaches might be best:
>  - add an extra callback to the API, something like pcb->recv_ext() with
> an associated means of setting a handler for this callback. 
>  - have a pcb->flag that selects whether to use the normal recv callback
> or the extended recv callback.
>  - have a compile time EXTENDED_RECV_CALLBACK definition that can be
> used to compile the extended recv callback feature out if others don't
> want it.
> 
> That way existing code doesn't need to be modified as the old callback
> remains the same.

Just to be clear, my suggestion meant that existing code doesn't have to
change either. But doesn't have the pcb overhead of an extra function
pointer+argument in the UDP PCB.

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------       Opinions==mine