[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Putting version information, description, copright into modules
- From: Peter Aronoff <telemachus@...>
- Date: Fri, 12 Feb 2016 11:09:24 -0500
On Friday, February 12, 2016 at 01:52PM, Roberto Ierusalimschy wrote:
> > > The manual says "names", not "variables".
> >
> > I'm sorry to be dense, but I don't see what you mean. Is a "name" simply
> > a toplevel variable? Does it mean something more specific here?
>
> name == identifier. It can be a global variable name, a field name,
> a parameter name, a local variable name, etc. All names are names :-)
Ok. Unfortunately both of your responses are too cryptic for me. I don't
know if you're answering my original question. And if you are answering,
I don't know what your answer is.
My thinking is that even though my module exports a table with an
identifier, a name, __VERSION, it's ok because that identifier is
namespaced within any program that imports (requires) it. (It's a field in
a table that no Lua-Rio code touches directly.)
Thus, even though the manual appears to say this is bad, there can't be any
actual conflict in practice.
Am I wrong? Or were you just commenting on my imprecise use of variable
instead of name?
Thanks, Peter
--
We have not been faced with the need to satisfy someone else's
requirements, and for this freedom we are grateful.
Dennis Ritchie and Ken Thompson, The UNIX Time-Sharing System
- 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