outrun, awesome! Will have to remember to throw some vexing expressions at you to parse I'm also fine with QFCL, in fact, that's how I was planning on referring to the library for short anyway (YAQL was an alternative that occurred to me, but perhaps that's a bit too playful).We might want to introduce the full name on the wiki, the first time we mention the abbreviation, perhaps in the "How to Contribute" section, s/QFCL depends/Quantitative Finance Code Library Project (QFCL) depends ?Incidentally, this --
http://www.wilmottwiki.com/wiki/index.p ... Contribute -- is 404, but shouldn't it work instead of the URL with "Qfcl"?By the way (regarding semanticum's question) -- I should probably just repeat this in this thread:To the extent that we can (which remains an open question), I'd be inclined to adopt the Boost Library Requirements and Guidelines pretty much verbatim (substituting the library name for "Boost" where applicable). Well, with possible exceptions, like "Aim first for clarity and correctness; optimization should be only a secondary concern in most Boost libraries." -- while correctness is fundamental and obviously has to overrule anything else, I'd be open to sacrifice clarity (which is a subjective quality) a little bit if significant optimization opportunities are present (e.g., parametric polymorphism & CRTP might be less "clear" to some than inclusion polymorphism & virtual member functions, but I wouldn't rule it out if its benefits would outweigh its costs in a given case).That includes all the pages under "Development" --
http://www.boost.org/development/index.html -- including "Testing" and "Boost Library Requirements and Guidelines" (including "Documentation").For reference:
http://www.boost.org/development/testin ... umentation