Namespaces
Variants
Views
Actions

Talk:cpp/links/libs

From cppreference.com

[edit] Splitting up boost

I see that boost containers are now listed on their own. Should we split up the rest of boost as well? boost.asio, boost.GIL, BGL, and boost.Spirit are a lot more notable (there's a book written just on BGL) than boost.heap or boost.bimap. --Cubbi 14:58, 21 August 2012 (PDT)

Yes, of course. I've created these sections only to see how they would look like, so any presentation issues could be solved. -- P12 15:02, 21 August 2012 (PDT)


[edit] Graphic Libraries link consistency

FTLK and GTKmm projects links point on home page, whereas Qt link directly point on documention (and avoid user find useful info such how to get it or license, etc). Shouldn't the current link (http://doc.qt.digia.com/) be replaced by http://qt.digia.com/product/ ? Deronnax 06:56, 12 October 2012 (PDT)

Feel free to change or add links. The {{lib}} template already allows to specify different links for the project page, download page and documentation page.

[edit] Pure C++, STL-free libraries

C++ gets a lot of undeserved hate from programmers working on bare-metal and other resource constrained systems - mostly because free and good C++/RTOS libraries are far and between. There is also no place to list them.

I hope the Embedded section will alleviate that sometime. A lot of those are not-so-free licensed (usually dual GPL) or hidden behind silly EULA forms, hope that will not be a problem. Ezdiy (talk) 13:42, 21 September 2013 (PDT)

I concur that it's worth to have Embedded section. However, I'm don't think adding libraries that can't be quickly evaluated (i.e. needs any additional step than just clicking download link) is a good idea. There are plenty of commercial options for each open-source library and we don't want to list them all. The requirement of available source seems to be a good compromise for now. --P12 11:18, 22 September 2013 (PDT)