faq.htm 6.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118
  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 Theme" content="none, default">
  7. <meta name="Microsoft Border" content="none, default">
  8. </head>
  9. <body bgcolor="#FFFFFF" text="#000000">
  10. <table border="1" bgcolor="#007F7F" cellpadding="2">
  11. <tr>
  12. <td bgcolor="#FFFFFF"><img src="../c++boost.gif" alt="c++boost.gif (8819 bytes)" WIDTH="277"
  13. HEIGHT="86"></td>
  14. <td><a href="../index.htm"><font face="Arial" color="#FFFFFF"><big>Home </big></font></a></td>
  15. <td><a href="../libraries.htm"><font face="Arial" color="#FFFFFF"><big>Libraries </big></font></a></td>
  16. <td><a href="../people.htm"><font face="Arial" color="#FFFFFF"><big>People </big></font></a></td>
  17. <td><a href="faq.htm"><font face="Arial" color="#FFFFFF"><big>FAQ </big></font></a></td>
  18. <td><a href="index.htm"><font face="Arial" color="#FFFFFF"><big>More </big></font></a></td>
  19. </tr>
  20. </table>
  21. <h1>Frequently Asked Questions</h1>
  22. <p><b>How is a library accepted for posting on the site?</b> An initial review by the
  23. library master filters out libraries which do not meet the absolute requirements (must be
  24. C++, ownership clear, reasonable format, etc.)&nbsp; The author is free to rework and
  25. resubmit libraries which do not pass initial muster. This is encouraged, particularly when
  26. reviewers like the idea behind a library but feel that details are lacking.</p>
  27. <p><b>Is there any assurance libraries actually work as claimed?</b> No. The review
  28. process will hopefully eliminate the most seriously flawed libraries, but a well
  29. constructed library with hidden defects is likely to slip through. Encouraging ordinary
  30. users to report their experience with a library is intended to address such concerns. </p>
  31. <p><b>How does someone submit a comment?</b>&nbsp; Send email to <a
  32. href="mailto:boost@egroups.com">boost@egroups.com</a>. </p>
  33. <p><strong>How does someone submit a library?</strong> See <a href="lib_guide.htm">Library
  34. Guidelines</a></p>
  35. <p><b>Are commercial libraries requiring a fee acceptable?</b> No. However, a library that
  36. a commercial enterprise makes available without fee is acceptable. If the description of
  37. the library makes a low-key plug for the supplier, that is acceptable as long as the
  38. library delivers real value and isn&#146;t just a Trojan horse for the plug.</p>
  39. <p><b>Are shareware libraries acceptable?</b> No. At least initially, only free libraries
  40. will be accepted.</p>
  41. <p><strong>Are open source license libraries acceptable?</strong>&nbsp; No, not currently.
  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, and 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 terms.<br>
  47. <br>
  48. This is subject to review for a particularly important piece of software, or as the
  49. industry changes.</p>
  50. <p><b>Must full source code be provided?</b> Yes, these are source code libraries.</p>
  51. <p><b>What about documentation?</b> A very simple library might be accepted with only a
  52. well commented header file. For more substantial libraries, some form of documentation is
  53. certainly going to be expected.&nbsp; HTML is the preferred form.</p>
  54. <p><b>Are platform specific libraries acceptable?</b> There is a preference for portable
  55. libraries. Libraries will be accepted that have portable interfaces but require platform
  56. specific implementations, as long as the author supplies implementations for a couple of
  57. disparate major operating systems.</p>
  58. <p><b>Must a library do useful work? </b>No. A library meant as a teaching example or
  59. demonstration might not actually do any work.</p>
  60. <p><b>Who owns the libraries?</b> Presumably many authors will copyright their libraries.
  61. Others authors may wish to place their libraries in the public domain. The Boost.org
  62. policy is to only accept libraries with a clear copyright notice.&nbsp; It is up to
  63. potential users to decide if they find the copyright terms acceptable, and to not use
  64. libraries with unacceptable copyrights.</p>
  65. <p><b>What support is available for the libraries?</b>&nbsp; Try the <a
  66. href="mailto:boost@egroups.com">boost@egroups.com</a> mailing list. </p>
  67. <p><b>Is there a relationship between Boost.org and the C++ Standards Committee?</b>
  68. &nbsp; No. The people who started Boost.org were all on the committee, but that was just
  69. happenstance.</p>
  70. <p><b>Will the Boost.org libraries become part of the next C++ Standard?</b>&nbsp; Some
  71. might, someday off in the future, but that is up to the standards committee.&nbsp; To the
  72. extent a library becomes &quot;existing practice&quot;, the likelihood increases that
  73. someone will propose it for future standardization. Submitting a library to Boost.org is
  74. one way to establish existing practice - as long as enough people are interested to
  75. download and use it!</p>
  76. <p><b>Is the site a commercial business?</b> No. It is just some people getting together
  77. as a kind of cyberspace civic association. If it ever needs to incorporate, it would be as
  78. non-profit organization.</p>
  79. <p><b>Is there any charge for submitting libraries or reviews to Boost.org?</b> No. Unlike
  80. the standards committees, you don&#146;t have to pay to volunteer!</p>
  81. <p><b>Will the site include material beyond libraries?</b> The main focus is on libraries,
  82. but if people contribute occasional articles or other material to make the site more
  83. interesting, that could be a nice fit.</p>
  84. <p><strong>How do I unzip the distribution files on my [whatever] computer?</strong>
  85. &nbsp; The .zip format is used for distribution because there are free decoders and
  86. encoders available for many, many different platforms. See the <a
  87. HREF="http://www.info-zip.org/pub/infozip/">Info-ZIP</a> web site, which includes a FAQ and
  88. much other useful information about the .zip format. Many commercial compressor-archiver
  89. utilities also support this format.</p>
  90. <p>-- End of FAQ --</p>
  91. <p>Revised May 17, 1999</p>
  92. </body>
  93. </html>
粤ICP备19079148号