I'd still use a case statement, because I think it's easier. This gets a bit obscure, though.
Code:
case $searchMonth:$searchYear in
:) echo no arguments;;
:*) echo year search;;
*:) echo month search;;
*) echo both;;
esac
This is not entirely robust in the face of random user input (if they give : as "year" it doesn't work right) but I guess you might be coping with that already earlier in your script.
One reason to prefer case over if is that you don't have to worry about an empty argument string; there are various tricks like if [ X"$input" = X ] but they're rather unsightly IMHO.
In my ksh script, if the conditions of a if statement are true, then do nothing; otherwise, execute some commands.
How do I write the "do nothing" statement in the following example?
Example:
if (( "$x"="1" && "$y"="a" && "$z"="happy" ))
then
do nothing
else
command
command
fi... (3 Replies)
Hi All,
I am using Unix ksh script.
I need to insert values to a table using the o/p from a slelect statement.
Can anybody Help!
My script looks like tihs.
---`sqlplus -s username/password@SID << EOF
set heading off
set feedback off
set pages 0
insert into ${TB_NAME}_D... (2 Replies)
I can't find anything wrong with this line of code, it works when there is one file in the directory but more than one i get a "too many arguements2 error
if ; then
am i missing something? (3 Replies)
Hello friends,
I have a boubt passing different arguments at a time for any one option in below code.
I would also like to check which option has been selected (any one of i, r, u ) so that whether or not matching argument passed can be verified.
for i and r - install and re-install -... (4 Replies)
I am writing a script in bash and want to perform the operation
I check number of arguments and make a print statement with the passes arguments
If I pass 3 arguments I will do
printf "$frmt" "$1" "$2" "$3"If I have 4 arguments I do
printf "$frmt" "$1" "$2" "$3" "$4"etc (4 Replies)
Hi
Am pretty new to C..
Am trying to pass the arguments from command line and use them in switch case statement..
i have tried the following
#include <stdlib.h>
main(int argc, char* argv)
{
int num=0;
if ( argc == 2 )
num = argv;
printf("%d is the num value",num);
switch ( num )
... (2 Replies)
Hello,
I have a question regarding the usage statement of a script.
I have 2 parameters "--pto" and "--pto_list". To start the script I will need one of them. Both together are not possible.
How this would be printed out within a usage statement?
My suggestion would be:
Usage:... (4 Replies)
Hi folks,
I have a scenario to convert the update statements into insert statements using shell script (awk, sed...) or in database using regex.
I have a bunch of update statements with all columns in a file which I need to convert into insert statements.
UPDATE TABLE_A SET COL1=1 WHERE... (0 Replies)
I'm stuck on a particular problem and need some guidance. I have a file with a name and a phone number in it (teledir.txt). I need to do a $# in a separate script to take a positional parameter and check to see if it is in the file. To quote the question:
If one argument is supplied, check... (6 Replies)
Discussion started by: Eric7giants
6 Replies
LEARN ABOUT NETBSD
lua
LUA(1) General Commands Manual LUA(1)NAME
lua - Lua interpreter
SYNOPSIS
lua [ options ] [ script [ args ] ]
DESCRIPTION
lua is the stand-alone Lua interpreter. It loads and executes Lua programs, either in textual source form or in precompiled binary form.
(Precompiled binaries are output by luac, the Lua compiler.) lua can be used as a batch interpreter and also interactively.
The given options (see below) are executed and then the Lua program in file script is loaded and executed. The given args are available to
script as strings in a global table named arg. If these arguments contain spaces or other characters special to the shell, then they
should be quoted (but note that the quotes will be removed by the shell). The arguments in arg start at 0, which contains the string
'script'. The index of the last argument is stored in arg.n. The arguments given in the command line before script, including the name of
the interpreter, are available in negative indices in arg.
At the very start, before even handling the command line, lua executes the contents of the environment variable LUA_INIT, if it is defined.
If the value of LUA_INIT is of the form '@filename', then filename is executed. Otherwise, the string is assumed to be a Lua statement and
is executed.
Options start with '-' and are described below. You can use '--' to signal the end of options.
If no arguments are given, then -v -i is assumed when the standard input is a terminal; otherwise, - is assumed.
In interactive mode, lua prompts the user, reads lines from the standard input, and executes them as they are read. If a line does not
contain a complete statement, then a secondary prompt is displayed and lines are read until a complete statement is formed or a syntax
error is found. So, one way to interrupt the reading of an incomplete statement is to force a syntax error: adding a ';' in the middle of
a statement is a sure way of forcing a syntax error (except inside multiline strings and comments; these must be closed explicitly). If a
line starts with '=', then lua displays the values of all the expressions in the remainder of the line. The expressions must be separated
by commas. The primary prompt is the value of the global variable _PROMPT, if this value is a string; otherwise, the default prompt is
used. Similarly, the secondary prompt is the value of the global variable _PROMPT2. So, to change the prompts, set the corresponding
variable to a string of your choice. You can do that after calling the interpreter or on the command line (but in this case you have to be
careful with quotes if the prompt string contains a space; otherwise you may confuse the shell.) The default prompts are "> " and ">> ".
OPTIONS
- load and execute the standard input as a file, that is, not interactively, even when the standard input is a terminal.
-e stat
execute statement stat. You need to quote stat if it contains spaces, quotes, or other characters special to the shell.
-i enter interactive mode after script is executed.
-l name
call require('name') before executing script. Typically used to load libraries.
-v show version information.
SEE ALSO luac(1)
http://www.lua.org/
DIAGNOSTICS
Error messages should be self explanatory.
AUTHORS
R. Ierusalimschy, L. H. de Figueiredo, and W. Celes
$Date: 2010/10/31 11:16:49 $ LUA(1)