Two minor (?) legal-related questions (empty lines and "Boost sponsorship")
Hi guys, the "how to apply to source files" entry at <http://www.boost.org/users/license.html> asks to leave an empty line before and after the comment block which contains copyright notice and license reference. I'm wondering if that was an advice from the lawyers who wrote the license or just a stylistic preference. Also, I just saw a BoostSponsorshipAgreement.pdf in the more/ subdirectory. What is it? -- Genny
On Wed, Jan 28, 2009 at 8:31 AM, Gennaro Prota <gennaro.prota@yahoo.com> wrote:
Hi guys,
the "how to apply to source files" entry at
<http://www.boost.org/users/license.html>
asks to leave an empty line before and after the comment block which contains copyright notice and license reference. I'm wondering if that was an advice from the lawyers who wrote the license or just a stylistic preference.
Stylistic.
Also, I just saw a BoostSponsorshipAgreement.pdf in the more/ subdirectory. What is it?
That's the legal document that was signed when Boost joined the Software Freedom Conservancy. The critical effect is that it makes Boost tax exempt under US tax rules and regulations. That makes BoostCon nontaxable, and cuts our administrative paperwork too. The Software Freedom Conservancy folks are also being very helpful in other ways with BoostCon finances. The agreement is working out well in practice. --Beman
Beman Dawes wrote:
the "how to apply to source files" entry at
<http://www.boost.org/users/license.html>
asks to leave an empty line before and after the comment block which contains copyright notice and license reference. I'm wondering if that was an advice from the lawyers who wrote the license or just a stylistic preference.
Stylistic.
So the inspection report tool will not be affected by missing empty lines?
Gennaro Prota wrote:
the "how to apply to source files" entry at <http://www.boost.org/users/license.html> asks to leave an empty line before and after the comment block which contains copyright notice and license reference. I'm wondering if that was an advice from the lawyers who wrote the license or just a stylistic preference.
Beman Dawes wrote:
Stylistic.
Thomas Klimpel wrote:
So the inspection report tool will not be affected by missing empty lines?
And would it be okay to have the comment block located /after/ the include guard macro? For my personal header files I prefer to have the include-guard defined at the very first line. Which makes life easier when I need to dive into the preprocessor output... Kind regards, Niels -- Niels Dekker http://www.xs4all.nl/~nd/dekkerware Scientific programmer at LKEB, Leiden University Medical Center
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Niels Dekker - mail address until 2010-10-10 Sent: 28 January 2009 15:13 To: boost@lists.boost.org Subject: Re: [boost] Two minor (?) legal-related questions (empty
linesand"Boost
sponsorship")
Gennaro Prota wrote:
the "how to apply to source files" entry at <http://www.boost.org/users/license.html> asks to leave an empty line before and after the comment block which contains copyright notice and license reference. I'm wondering if that was an advice from the lawyers who wrote the license or just a stylistic preference.
Beman Dawes wrote:
Stylistic.
Thomas Klimpel wrote:
So the inspection report tool will not be affected by missing empty lines?
And would it be okay to have the comment block located /after/ the include guard macro? For my personal header files I prefer to have the include-guard defined at the very first line. Which makes life easier when I need to dive into the preprocessor output...
Well - what about Doxygen comments like /*! \file svg_2d_plot.hpp \brief Create 2D plots in Scalable Vector Graphic (SVG) format. \author Jacob Voytko & Paul A. Bristow */ // Copyright Jacob Voytko 2007 // Copyright Paul A. Bristow 2007, 2008, 2009 // Use, modification and distribution are subject to the // Boost Software License, Version 1.0. // (See accompanying file LICENSE_1_0.txt // or copy at http://www.boost.org/LICENSE_1_0.txt) #ifndef BOOST_SVG_SVG_2D_PLOT_HPP #define BOOST_SVG_SVG_2D_PLOT_HPP .... This *feels* as though it should come first? But I think that a consistent recommended style is the key thing. Paul --- Paul A. Bristow Prizet Farmhouse Kendal, UK LA8 8AB +44 1539 561830, mobile +44 7714330204 pbristow@hetp.u-net.com
participants (5)
-
Beman Dawes -
Gennaro Prota -
Niels Dekker - mail address until 2010-10-10 -
Paul A. Bristow -
Thomas Klimpel