faq.htm 7.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134
  1. <html>
  2. <head>
  3. <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  4. <title>FAQ</title>
  5. <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
  6. <meta name="Microsoft Border" content="none, default">
  7. </head>
  8. <body bgcolor="#FFFFFF" text="#000000">
  9. <table border="1" bgcolor="#007F7F" cellpadding="2">
  10. <tr>
  11. <td bgcolor="#FFFFFF"><img src="../c++boost.gif" alt="c++boost.gif (8819 bytes)" WIDTH="277"
  12. HEIGHT="86"></td>
  13. <td><a href="../index.htm"><font face="Arial" color="#FFFFFF"><big>Home </big></font></a></td>
  14. <td><a href="../libs/libraries.htm"><font face="Arial" color="#FFFFFF"><big>Libraries </big></font></a></td>
  15. <td><a href="../people/people.htm"><font face="Arial" color="#FFFFFF"><big>People </big></font></a></td>
  16. <td><a href="faq.htm"><font face="Arial" color="#FFFFFF"><big>FAQ </big></font></a></td>
  17. <td><a href="index.htm"><font face="Arial" color="#FFFFFF"><big>More </big></font></a></td>
  18. </tr>
  19. </table>
  20. <h1>Frequently Asked Questions</h1>
  21. <p><b>How is a library accepted for posting on the site?</b> An initial review by the
  22. library master filters out libraries which do not meet the absolute requirements (must be
  23. C++, ownership clear, reasonable format, etc.)&nbsp; The author is free to rework and
  24. resubmit libraries which do not pass initial muster. This is encouraged, particularly when
  25. reviewers like the idea behind a library but feel that details are lacking.</p>
  26. <p><b>Is there any assurance libraries actually work as claimed?</b> No. The review
  27. process will hopefully eliminate the most seriously flawed libraries, but a well
  28. constructed library with hidden defects is likely to slip through. Encouraging ordinary
  29. users to report their experience with a library is intended to address such concerns. </p>
  30. <p><b>How does someone submit a comment?</b>&nbsp; Send email to <a
  31. href="mailto:boost@egroups.com">boost@egroups.com</a>. </p>
  32. <p><strong>How does someone submit a library?</strong> See <a href="lib_guide.htm">Library
  33. Guidelines</a></p>
  34. <p><b>Are commercial libraries requiring a fee acceptable?</b> No. However, a library that
  35. a commercial enterprise makes available without fee is acceptable. If the description of
  36. the library makes a low-key plug for the supplier, that is acceptable as long as the
  37. library delivers real value and isn&#146;t just a Trojan horse for the plug.</p>
  38. <p><b>Are shareware libraries acceptable?</b> No. At least initially, only free libraries
  39. will be accepted.</p>
  40. <p><strong>Are open source license libraries acceptable?</strong>&nbsp; Some
  41. are, many are not.
  42. Open source licenses often require redistribution or availability of source code,
  43. inclusion of license document with machine-executable redistribution, give the initial
  44. developer rights to licensee modifications, or need a lawyer to understand.&nbsp; These
  45. would be immediate disqualifications for many business, commercial, and consumer
  46. applications. Boost aims to avoid subjecting users to hard-to-comply-with license
  47. terms. See <a href="lib_guide.htm##License">License requirements</a>.<br>
  48. <br>
  49. This is subject to review for a particularly important piece of software, or as the
  50. industry changes.</p>
  51. <p><b>Must full source code be provided?</b> Yes, these are source code libraries.</p>
  52. <p><b>What about documentation?</b> A very simple library might be accepted with only a
  53. well commented header file. For more substantial libraries, some form of documentation is
  54. certainly going to be expected.&nbsp; HTML is the preferred form.</p>
  55. <p><b>Are platform specific libraries acceptable?</b> There is a preference for portable
  56. libraries. Libraries will be accepted that have portable interfaces but require platform
  57. specific implementations, as long as the author supplies implementations for a couple of
  58. disparate major operating systems.</p>
  59. <p><b>Must a library do useful work? </b>No. A library meant as a teaching example or
  60. demonstration might not actually do any work.</p>
  61. <p><b>Who owns the libraries?</b> Presumably many authors will copyright their libraries.
  62. Others authors may wish to place their libraries in the public domain. The Boost.org
  63. policy is to only accept libraries with a clear copyright notice.&nbsp; It is up to
  64. potential users to decide if they find the copyright terms acceptable, and to not use
  65. libraries with unacceptable copyrights.</p>
  66. <p><b>What support is available for the libraries?</b>&nbsp; Try the <a
  67. href="mailto:boost@egroups.com">boost@egroups.com</a> mailing list. </p>
  68. <p><b>Is there a formal relationship between Boost.org and the C++ Standards Committee?</b>
  69. &nbsp; No. The people who started Boost.org were all on the committee, but that was just
  70. happenstance.</p>
  71. <p><b>Will the Boost.org libraries become part of the next C++ Standard?</b>&nbsp; Some
  72. might, someday off in the future, but that is up to the standards committee.&nbsp; To the
  73. extent a library becomes &quot;existing practice&quot;, the likelihood increases that
  74. someone will propose it for future standardization. Submitting a library to Boost.org is
  75. one way to establish existing practice - as long as enough people are interested to
  76. download and use it!</p>
  77. <p><b>Is the web site a commercial business?</b> No. It is just some people getting together
  78. as a kind of cyberspace civic association. If it ever needs to incorporate, it would be as
  79. non-profit organization.</p>
  80. <p><b>Is there any charge for submitting libraries or reviews to Boost.org?</b> No. Unlike
  81. the standards committees, you don&#146;t have to pay to volunteer!</p>
  82. <p><b>Will the site include material beyond libraries?</b> The main focus is on libraries,
  83. but if people contribute occasional articles or other material to make the site more
  84. interesting, that could be a nice fit.</p>
  85. <p><strong>How do I download the libraries?</strong>
  86. &nbsp; See <a href="../libs/libraries.htm#Download">Download</a> instructions.</p>
  87. <p><b>Why isn't there a separate boost mailing list for my favorite
  88. library?&nbsp;</b> One of the reasons for boost's success has been the cross-pollination of ideas between diverse library
  89. projects and the occasional look into other threads by otherwise uninterested parties. The more people participate, the less they tend to be annoyed by
  90. "noise".</p>
  91. <p><b>How can I cope with the large volume of boost mailing list messages?</b>&nbsp;
  92. One approach is to use the eGroups digest option; that cuts the email blizzard
  93. down to about three (long) messages per day, so you can glance over the subjects
  94. summary at the top and quickly read what you think is important.&nbsp;The
  95. eGroups &quot;no mail/web only&quot; option is best if you just occasionally
  96. want to look at messages.</p>
  97. <p>Yet another approach is to use your email program's capabilities to filter messages and automatically
  98. transfer them into several boost folders.&nbsp;Then only read the folders you
  99. care about. Boost list posters are
  100. encouraged to include keywords in the subject like &quot;thread&quot;,
  101. &quot;review&quot;, and &quot;CVS&quot; to aid message filtering.</p>
  102. <hr>
  103. <p>Revised <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->08 December, 2000<!--webbot bot="Timestamp" endspan i-checksum="38516" -->
  104. </p>
  105. </body>
  106. </html>
粤ICP备19079148号