On Fri, March 14, 2014 8:53 pm, Martin Townsend wrote: > Thanks Phoebe, I'll probably get shot down for proposing this as _sa is > standard nomenclature but couldn't we use ieee802154_saddr or > iee802154_sockaddr to avoid the unfortunate similarity with source > address and avoid statements like this: > > + struct ieee802154_addr_sa sa; > + struct ieee802154_addr_sa da;
ieee802154_sockaddr and sockaddr_ieee802154 sounds too similar to me. I wanted to differentiate between the addr structs that the stack should use versus the addr structs current userspace expects (if on somewhat weird paths). Using anything other than ieee802154_addr for the proper addrs used inside the stack also didn't ring well with me, so I just went with the first thing that came to my mind. We'll see how that goes :) Using other names is of course possible, but then again the *_sa form should ideally just go away. ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ Linux-zigbee-devel mailing list Linux-zigbee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
