[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Putting version information, description, copright into modules
- From: Phil Leblanc <philanc@...>
- Date: Fri, 12 Feb 2016 13:30:39 -0500
> We usually put some information strings into our modules, e.g.
> [ ..._COPYRIGHT, _DESCRIPTION, _VERSION ...]
> How do other module-writer handle such?
I wonder how other module-*users* handle such.
_VERSION may be useful to make choices according to the version of the
API or of the implementation.
But is the copyright or description (or author or ...) string useful
for the program using the module?
I think that the right place for all these metadata is in source code
comments, LICENSE files, documentation, rocks and such.
Regarding the leading underscore, I am not a big fan either. Do we
really spell _VERSION instead of VERSION because we also have a
different 'VERSION' constant in our own module? :-) but at least
it is consistent with the Lua global _VERSION constant.
- References:
- Putting version information, description, copright into modules, Marc Balmer
- Re: Putting version information, description, copright into modules, Daurnimator
- Re: Putting version information, description, copright into modules, Peter Aronoff
- Re: Putting version information, description, copright into modules, Roberto Ierusalimschy
- Re: Putting version information, description, copright into modules, Peter Aronoff
- Re: Putting version information, description, copright into modules, Roberto Ierusalimschy
- Re: Putting version information, description, copright into modules, Peter Aronoff
- Re: Putting version information, description, copright into modules, Philipp Janda
- Re: Putting version information, description, copright into modules, Peter Aronoff