Re: [lwip-devel] Extended udp_recv callback

[Kieran Mansley]

On Wed, 2009-01-14 at 12:20 +0100, Jakob Stoklund Olesen wrote:
> Kieran Mansley wrote:
> > Couple of style points:
> >  - let's try and keep our naming consistent.  At the moment we have
> > udp_recv() to set the recv callback (note no "callback" in that function
> > name), so try to add something that logically follows from that.
> 
> I gathered from Jonathan's comments that he prefers more verbose API
> functions. I have also been confused buy the meaning of udp_recv and
> tcp_accept myself.

For the record I'd prefer that too, but don't want to change the API by
renaming everything else and consistency is better than a bit of both.

> How about udp_ext_recv() ?
> 
> typedef udp_recv_callback_t
> typedef udp_ext_recv_callback_t
> 
> >  - I'm not a big fan of using "raw" again: it has lots of other meanings
> > already (raw API, raw socket, etc) and so having another use will only
> > confuse things.
> 
> Alright. s/RAW/EXT/ ?

Fine, thanks.

Kieran