On Feb 7, 2014, at 3:36 PM, Tom Browder wrote: > Okay, is there an existing private header at global scope (./include) > that is a good candidate to hold them?
Headers in the top-level include/ directory are public API by definition. They're the ones that get installed and the intent is to get them all fully documented, modularized into sub-directories, and made smaller overall. Private headers go into the src subdirectory (e.g., into src/libbu) and none should be installed. If you search for *.h, you'll find several of them. Care should be taken to minimize what needs to be declared to exactly what is actually used in multiple files, not just declared as being available for use. We don't want to end up with secret APIs underneath public APIs unnecessarily... :) Cheers! Sean ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
