【问题标题】:Is placement and format of copyright statement relevant? [closed]版权声明的位置和格式是否相关? [关闭]
【发布时间】:2010-08-21 01:22:49
【问题描述】:

我见过的每个软件,都在文件开头包含版权声明,并且需要大量注释。因此你必须向下滚动才能看到代码,这有点烦人,尤其是当代码本身很短时。

我认为将版权声明保留在文件的底部并将所有条款加入单行(或几行)会更好。这只是为了满足形式问题。 LICENSE 文件中提供了易于阅读的版本。

但是到目前为止我还没有见过这样的做法。这只是部落习俗还是有原因?

编辑:这里以 GNU STL 库中的 为例:

// <list> -*- C++ -*-

// Copyright (C) 2001, 2002, 2003 Free Software Foundation, Inc.
//
// This file is part of the GNU ISO C++ Library.  This library is free
// software; you can redistribute it and/or modify it under the
// terms of the GNU General Public License as published by the
// Free Software Foundation; either version 2, or (at your option)
// any later version.

// This library is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
// GNU General Public License for more details.

// You should have received a copy of the GNU General Public License along
// with this library; see the file COPYING.  If not, write to the Free
// Software Foundation, 59 Temple Place - Suite 330, Boston, MA 02111-1307,
// USA.

// As a special exception, you may use this file as part of a free software
// library without restriction.  Specifically, if other files instantiate
// templates or use macros or inline functions from this file, or you compile
// this file and link it with other files to produce an executable, this
// file does not by itself cause the resulting executable to be covered by
// the GNU General Public License.  This exception does not however
// invalidate any other reasons why the executable file might be covered by
// the GNU General Public License.

/*
 *
 * Copyright (c) 1994
 * Hewlett-Packard Company
 *
 * Permission to use, copy, modify, distribute and sell this software
 * and its documentation for any purpose is hereby granted without fee,
 * provided that the above copyright notice appear in all copies and
 * that both that copyright notice and this permission notice appear
 * in supporting documentation.  Hewlett-Packard Company makes no
 * representations about the suitability of this software for any
 * purpose.  It is provided "as is" without express or implied warranty.
 *
 *
 * Copyright (c) 1996,1997
 * Silicon Graphics Computer Systems, Inc.
 *
 * Permission to use, copy, modify, distribute and sell this software
 * and its documentation for any purpose is hereby granted without fee,
 * provided that the above copyright notice appear in all copies and
 * that both that copyright notice and this permission notice appear
 * in supporting documentation.  Silicon Graphics makes no
 * representations about the suitability of this software for any
 * purpose.  It is provided "as is" without express or implied warranty.
 */

/** @file list
 *  This is a Standard C++ Library header.  You should @c #include this header
 *  in your programs, rather than any of the "st[dl]_*.h" implementation files.
 */

#ifndef _GLIBCXX_LIST
#define _GLIBCXX_LIST 1

#pragma GCC system_header

#include <bits/functexcept.h>
#include <bits/stl_algobase.h>
#include <bits/allocator.h>
#include <bits/stl_construct.h>
#include <bits/stl_uninitialized.h>
#include <bits/stl_list.h>

#ifndef _GLIBCXX_EXPORT_TEMPLATE
# include <bits/list.tcc>
#endif

#ifdef _GLIBCXX_DEBUG
# include <debug/list>
#endif

#endif /* _GLIBCXX_LIST */

【问题讨论】:

    标签: licensing code-formatting copyright-display


    【解决方案1】:

    虽然不一定是自定义或要求,但标准倾向于规定 cmets 应进行任何代码定义。以NDOC notation为例。

    对于版权,您通常希望人们在继续使用您的代码之前阅读它(EULA 始终显示在安装程序的开头处)。如果将版权声明放在代码定义的底部,则很有可能会被忽略。

    【讨论】:

    • 是的,但我是关于通常不是文档评论的许可证通知。
    • 尽管如此,人们还是倾向于坚持他们所知道的。大多数人都把版权放在首位,那为什么要偏离呢?就个人而言,我认为把它放在底部没有什么问题,但如果其他人都在跳桥,你还不如加入他们,对吧? =p
    【解决方案2】:

    如果您将版权注释放在文件的开头,则版权声明在有人打开文件时可见(如果打开文件的人没有使用自动转到最后访问行的编辑器)。如果将版权注释放在文件的底部,人们需要滚动到最后才能看到版权,这是人们首先应该有兴趣看到的。

    【讨论】:

    • 您是否阅读了所有来源以获取许可信息?我从不同的地方获得有关特定软件许可的信息,例如文档、网站或许可文件。如果我对特定软件的开发感兴趣,无论如何我都会找到版权声明。我将受益于更轻松地访问代码,而不是每次打开文件时都看到版权。
    • @doc:如果源文件中有版权注释,我会优先处理。在某些情况下,程序可能包含许可证与整体许可证不同(或略有不同)的源文件,或者该文件是由不同的人编写的;在这些情况下,版权(或许可)评论可能与其他地方报告的不同。
    猜你喜欢
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2020-07-19
    • 2020-11-18
    • 1970-01-01
    • 2012-05-22
    • 2015-08-08
    相关资源
    最近更新 更多