Hi all,

On 2010-11-29 <19:17:00>, Wolfgang Schuster wrote:
> 
> Am 18.11.2010 um 19:33 schrieb luigi scarso:
> 
> > I just want to register my namespace(s) to be sure to avoid conflicts
> > not only for modules but also for lua code
> 
> Good idea and it’s not a problem to reserve „lscarso“ for you but i ask
> myself which of these tables (luat-ini.lua) are available for users:
> 
> userdata      = userdata      or { } -- might be used
> thirddata     = thirddata     or { } -- might be used
> moduledata    = moduledata    or { } -- might be used
> documentdata  = documentdata  or { } -- might be used
> parametersets = parametersets or { } -- experimental
> 
> document      = document      or { }

If I may add to this question: I am using “job.variables” as kind
of base for my private use area (not for modules, though) -- bad
habit or valid alternative?

Thanks, Philipp

> 
> Wolfgang
> 
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________

-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

Attachment: pgpKJlVrrCXyU.pgp
Description: PGP signature

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Reply via email to