On Tue, May 13, 2014 at 11:31 AM, Tom Browder <tom.brow...@gmail.com> wrote: > On Tue, May 13, 2014 at 11:09 AM, Christopher Sean Morrison >> I'm leery of features getting implemented without a >> specific known use case (i.e., "if you build it, they will come"), but
The use case is a set of D bindings to add to the existing D collection at: https://github.com/D-Programming-Deimos >> I see no issue doing that in a branch. > > Maybe it would be better to do such a project in a like umbrella group such > as: > > https://github.com/D-Programming-Deimos Hm, those projects seem to point back to the upstream repos. Maybe the binding code should be here until it is working. I guess a branch would work, but working on the trunk shouldn't interfere with "normal" builds if the appropriate option (default "NO") is not turned on. It would be easier to avoid doing constant merges to keep up with the trunk. FYI, Repository impact of a D binding (branch or trunk): The current header footprint (at rev 60614) consists of 1290 source headers (*.h) in the tree (not counting generated ones) consisting of 370,197 lines (including comments and macros) and sized at about 15 Mb (out of about 615 Mb of total source). The impact of a D binding as far as I know at the moment is one file per header, so, ballparkly-speaking, adding the D bindings to the source would add roughly the same amount of resources as the current header footprint: an additional 2.44%. Best, -Tom ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
