lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]


On Fri, Aug 6, 2010 at 1:31 PM, Petite Abeille <petite.abeille@gmail.com> wrote:
>
> On Aug 6, 2010, at 10:25 PM, Jonathan Castello wrote:
>
>>> Hmmm... perhaps I'm missing something very obvious, but how does one name a module in such a setup?
>>
>> I think it was mentioned earlier that the caller would decide where
>> the module would be put and under what name, i.e.:
>
> Hmmm... why should the caller need to know such details? The caller only need to know a module name, not the details of it physical representation (e.g. file or not).
>
>

I don't understand what you mean. require() doesn't expose these
details, all the caller needs to decide is what to call it and whether
they want it local. The sematics of package.path and package.cpath
haven't changed to my knowledge.

-- 
~Jonathan