On Dec 22, 2007 4:15 AM, Asko Kauppi <[EMAIL PROTECTED]> wrote: > > Hi, guys. > > I think it would be good to bring this up with the authors. Being > able to follow the native restrictions is helpful for using Lua in > system scripting, and generally in line with Lua's scalable attitude. > The proposed alternative of making 'arg' a userdata which would proxy > to the operating system's strings sounds small code, efficient and in > every way preferable to me. > > Maybe that should be made into a patch and proposed to the authors, > then? > > There are some issues, though. > > - If 'arg' is being phased out at some point (it no longer is needed > for anything, really) how to give the unlimited functionality to > '...' at the chunk level? > > - If 'arg' remains, it could work "unlimited" whereas the '...' way > would carry the limits.
To me the solution is simple-- the command line arguments should be available as a list via select(1, ...). In other words the standard Lua interpreter passes command line args to the chunk as a list argument-- no magic involved. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
