mirror of
https://github.com/boostorg/more.git
synced 2024-12-27 23:40:13 +08:00
General update including added links
[SVN r10724]
This commit is contained in:
parent
3d27eeeab2
commit
0d2ece91c9
51
faq.htm
51
faq.htm
@ -32,19 +32,23 @@ href="mailto:boost@yahoogroups.com">boost@yahoogroups.com</a> mailing list. </p>
|
||||
<p><b>What do the Boost version numbers mean? </b>The scheme is x.y.z, where x is incremented only for massive changes, such as a reorganization of many libraries, y is incremented whenever a new library is added, and z is incremented for maintenance releases. y and z are reset to 0 if
|
||||
the value to the left changes. <br>
|
||||
<br>
|
||||
<b>Is there any assurance libraries actually work as claimed?</b> No. The review
|
||||
process will hopefully eliminate the most seriously flawed libraries, but a well
|
||||
constructed library with hidden defects is likely to slip through. Encouraging ordinary
|
||||
users to report their experience with a library is intended to address such concerns.
|
||||
See the <a href="../status/compiler_status.html">Status</a> page for an
|
||||
indication of how well a library works on specific platforms. </p>
|
||||
|
||||
<p>
|
||||
<b>How can the Boost libraries be used successfully for important projects?
|
||||
</b>Many of the Boost libraries are actively maintained and improved, so backward compatibility with prior version isn't always possible. Deal with this by freezing the version of the Boost libraries used by your project. Only upgrade at points in your project's life cycle where a bit of change will not cause problems. Individual bug fixes can always be obtained from the CVS repository. </p>
|
||||
|
||||
<p><b>How is a library accepted for posting on the site?</b>
|
||||
See <a href="submission_process.htm">Library Submission Process</a></p>
|
||||
|
||||
<p><b>Is there any assurance libraries actually work as claimed?</b> No. The review
|
||||
process will hopefully eliminate the most seriously flawed libraries, but a well
|
||||
constructed library with hidden defects is likely to slip through. Encouraging ordinary
|
||||
users to report their experience with a library is intended to address such concerns. </p>
|
||||
|
||||
<p><b>How does someone submit a comment?</b> Send email to <a
|
||||
href="mailto:boost@yahoogroups.com">boost@yahoogroups.com</a>. </p>
|
||||
<p><b>How does someone submit a Formal Review comment?</b> Send email to <a
|
||||
href="mailto:boost@yahoogroups.com">boost@yahoogroups.com</a>. See the <a href="formal_review_process.htm">Formal
|
||||
Review</a> page for more information. </p>
|
||||
|
||||
<p><strong>How does someone submit a library?</strong> See <a href="lib_guide.htm">Library
|
||||
Guidelines</a></p>
|
||||
@ -54,7 +58,7 @@ a commercial enterprise makes available without fee is acceptable. If the descri
|
||||
the library makes a low-key plug for the supplier, that is acceptable as long as the
|
||||
library delivers real value and isn’t just a Trojan horse for the plug.</p>
|
||||
|
||||
<p><b>Are shareware libraries acceptable?</b> No. At least initially, only free libraries
|
||||
<p><b>Are shareware libraries acceptable?</b> No. Only free libraries
|
||||
will be accepted.</p>
|
||||
|
||||
<p><strong>Are open source license libraries acceptable?</strong> Some
|
||||
@ -83,22 +87,31 @@ disparate major operating systems.</p>
|
||||
<p><b>Must a library do useful work? </b>No. A library meant as a teaching example or
|
||||
demonstration might not actually do any work.</p>
|
||||
|
||||
<p><b>Can an existing library be accepted by Boost?</b> Yes, although it would
|
||||
have to be "Boostified" to meet the requirements. The Boost
|
||||
Graph and Regex libraries are examples of libraries which began life elsewhere.</p>
|
||||
|
||||
<p><b>Who owns the libraries?</b> Presumably many authors will copyright their libraries.
|
||||
Others authors may wish to place their libraries in the public domain. The Boost.org
|
||||
policy is to only accept libraries with a clear copyright notice. It is up to
|
||||
potential users to decide if they find the copyright terms acceptable, and to not use
|
||||
libraries with unacceptable copyrights.</p>
|
||||
policy is to only accept libraries with a clear copyright notice and meeting the
|
||||
<a href="lib_guide.htm#License">License requirements</a>.. It is up to
|
||||
potential users to decide if the terms acceptable, and not to use
|
||||
libraries with unacceptable copyrights or licenses.</p>
|
||||
|
||||
<p><b>Is there a formal relationship between Boost.org and the C++ Standards Committee?</b>
|
||||
No. The people who started Boost.org were all on the committee, but that was just
|
||||
happenstance.</p>
|
||||
No, although there is a strong informal relationship in that many members
|
||||
of the committee participate in Boost, and the people who started Boost were all
|
||||
committee members.</p>
|
||||
|
||||
<p><b>Will the Boost.org libraries become part of the next C++ Standard?</b> Some
|
||||
might, someday off in the future, but that is up to the standards committee. To the
|
||||
extent a library becomes "existing practice", the likelihood increases that
|
||||
someone will propose it for future standardization. Submitting a library to Boost.org is
|
||||
one way to establish existing practice - as long as enough people are interested to
|
||||
download and use it!</p>
|
||||
might, someday, but that is up to the standards committee. Committee
|
||||
members who also participate in Boost will definitely be proposing at least some
|
||||
Boost libraries for standardization.</p>
|
||||
|
||||
<p>Libraries which are "existing practice" are most likely to be
|
||||
accepted by the C++ committee for future standardization. Having a library
|
||||
accepted by Boost is
|
||||
one way to establish existing practice.</p>
|
||||
|
||||
<p><b>Is the web site a commercial business?</b> No. It is just some people getting together
|
||||
as a kind of cyberspace civic association. If it ever needs to incorporate, it would be as
|
||||
@ -131,7 +144,7 @@ encouraged to include keywords in the subject like "thread",
|
||||
|
||||
<hr>
|
||||
|
||||
<p>Revised <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->24 April, 2001<!--webbot bot="Timestamp" endspan i-checksum="29814" -->
|
||||
<p>Revised <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->30 July, 2001<!--webbot bot="Timestamp" endspan i-checksum="21063" -->
|
||||
</p>
|
||||
</body>
|
||||
</html>
|
||||
|
Loading…
Reference in New Issue
Block a user