On Mon, Jul 02, 2018 at 10:57:17AM +0000, Anders Selhammer wrote: > That's true, but there is also a pattern to start each global function with > the name > of the file, like: > > port_open() > clock_create() > transport_open()
Well, the files are named for the objects. In the case of port.c, the port object is getting so large that I want to start putting new functionality into separate files. It used to be monolithic, but now we have many sub-areas like OC, BC, TC, and unicast... I am not a fan of renames and refactoring "just because". This carries the risk of breaking things only for cosmetic benefit (for example by typos). As we add and change real functionality, that is time to fix coding style and other purely cosmetic issues. Thanks, Richard ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
