[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Lua as replacement for Bash scripting
- From: Alexander Gladysh <agladysh@...>
- Date: Tue, 13 Jul 2010 01:18:07 +0400
> I share Javier and Florian's feelings -- Peter's os.execute wrapper
> already escapes properly all arguments. To me the very point of having
> stuff such as sh.run.command(arg1, arg2) is to avoid escaping.
If we have this function, is there a reason to hide it from the user?
> I don't mind having functions for string expansion, but I think we'll
> end up using them very little. I think we'll get a better feel about
> this when we rewrite some shell-script in our hypothetic API, as you
> suggested.
If we would use string expansion very little, IMO, we must drop it.
The most usable variant of string expansion uses debug library — which
is extra burden. Other variants are trivial to implement and need not
to be included in the lua-shellscript.
Alexander.
- References:
- Lua as replacement for Bash scripting, Alexander Gladysh
- Re: Lua as replacement for Bash scripting, Jerome Vuarand
- Re: Lua as replacement for Bash scripting, Alexander Gladysh
- Re: Lua as replacement for Bash scripting, Jerome Vuarand
- Re: Lua as replacement for Bash scripting, Hisham
- Re: Lua as replacement for Bash scripting, Alexander Gladysh
- Re: Lua as replacement for Bash scripting, Florian Weimer
- Re: Lua as replacement for Bash scripting, Javier Guerra Giraldez
- Re: Lua as replacement for Bash scripting, Alexander Gladysh
- Re: Lua as replacement for Bash scripting, Hisham