Sponsored Content
Full Discussion: Eval set -- and more
Top Forums UNIX for Beginners Questions & Answers Eval set -- and more Post 302990778 by mohca2020 on Tuesday 31st of January 2017 05:57:25 PM
Old 01-31-2017
Question Eval set -- and more

Hello everyone,

I am taking a course on Lynda and they show this code below. I didn't fully understand some parts. Please see the questions within the code.

Thank you for your input and time.

Regards,

Code:
function usage {
   echo Options are -r -h -b -x --branch --version --help --exclude
   exit 1
}
function handleopts {
    OPTS=`getopt -o r:hb::x: -l exclude: -l branch::  -l help -l version -- "$@"`
#### Question 1: How does the "-- $@" work here ####
    if [ $? != 0 ]
    then
        echo ERROR parsing arguments >&2
        exit 1
    fi
    eval set -- "$OPTS"
#### Question 2: I understand that set -- $variable sets the content of $variable to the positional parameters, but how does it work here? What are the PP here? ####
    while true ; do
        case "$1" in
            -r ) rightway=$2 
                shift 2;;
#### Question 3: I assume that shift 2 means shift shift, but why is it needed here? ####
            --version ) echo "Version 1.2"; 
                 exit 0;;
            -h | --help ) usage; 
                 shift;;
            -b | --branch) 
                case "$2" in
                "") branchname="default"  ; shift 2 ;;
                 *) branchname="$2" ; shift 2 ;;
                esac ;;
            --) shift; break;;
        esac
    done
    if [ "$#" -ne 0 ]
    then
	echo Error extra command line arguments "$@"
	usage
    fi
}
rightway=no
handleopts $@
echo rightway = $rightway
echo branchname = $branchname


Last edited by rbatte1; 02-01-2017 at 09:16 AM.. Reason: Spelling corrections
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

using eval with set, wc, and expr

Okay this is a mess, I'm trying to assign variables with variables in a for-loop. Here is what i have for code. The syntax is not good. Given the following script: #! /bin/csh foreach site (ABC DEF GHI) eval set \t$${site}sf = ``wc -l \$${site}.sf | awk '{print $1}'`` eval set... (2 Replies)
Discussion started by: wxornot
2 Replies

2. Shell Programming and Scripting

EVal

Hi All, I'm running some encrypted data through a script I wrote. In order to do this, I'm using eval to resolve some of my variables. At the moment, when I use eval to resolve, it strips out some of my encrypted values, and totally drops some others. For example if I have the value ab1"3 it drops... (1 Reply)
Discussion started by: Khoomfire
1 Replies

3. Shell Programming and Scripting

KSH script eval(?) to set variable

first of all, thanks to all on this board, it has been a huge resource to answer most of my questions! I am stuck on something that should really be simple, and was looking for some help.. I am using KSH on solaris and working on a script to move containers from server to server. Where i am... (4 Replies)
Discussion started by: tksol
4 Replies

4. Shell Programming and Scripting

eval help

I am trying to expand the variable $user in my alias command and tried several variations of eval but can't seem to get it to work. The end result should be either: oracle_user='sudo su - oracle ' or oracle_user='sudo su - oracle1 ' user=$(grep '^oracle:' /etc/passwd | cut... (5 Replies)
Discussion started by: BeefStu
5 Replies

5. Shell Programming and Scripting

eval

hi all, Am trying to add some code to a ksh script and i dont understand how an eval function is used : _var=$1 _conceal=$2 eval _val=\$${_var} can someone shed some light on what the eval function in the above context means/does ?? thanks. (4 Replies)
Discussion started by: cesarNZ
4 Replies

6. Shell Programming and Scripting

Strange result of eval, how does eval really work with ssh?

Hi all, some small script with eval turned me to crazy. my OS is linux Linux s10-1310 2.6.16.53-0.8.PTF.434477.3.TDC.0-smp #1 SMP Fri Aug 31 06:07:27 PDT 2007 x86_64 x86_64 x86_64 GNU/Linux below script works well #!/bin/bash eval ssh remotehost date eval ssh remotehost ls below... (1 Reply)
Discussion started by: summer_cherry
1 Replies

7. Shell Programming and Scripting

Error in eval eval command to print html tags

anyone has any info on why this is complaining??? vivek@vivek-c5e55ef2e ~/TAC $ zoneCounter=1 vivek@vivek-c5e55ef2e ~/TAC $ optUsage1=23% vivek@vivek-c5e55ef2e ~/TAC $ eval eval echo "<th>Zone $zoneCounter </th><th align=\"left\"> \$optUsage$zoneCounter </th>" -bash: syntax error... (1 Reply)
Discussion started by: vivek d r
1 Replies

8. Shell Programming and Scripting

Error in eval eval command to print html tags

anyone has any info on why this is complaining??? vivek@vivek-c5e55ef2e ~/TAC $ zoneCounter=1 vivek@vivek-c5e55ef2e ~/TAC $ optUsage1=23% vivek@vivek-c5e55ef2e ~/TAC $ eval eval echo "<th>Zone $zoneCounter </th><th align=\"left\"> \$optUsage$zoneCounter </th>" -bash: syntax error... (13 Replies)
Discussion started by: vivek d r
13 Replies

9. Shell Programming and Scripting

Eval

thank you (35 Replies)
Discussion started by: ratnalein88
35 Replies

10. Shell Programming and Scripting

Getopt eval set parameters not happening when the script is called through an application!

Hi, There is an Informatica tool through which unix scripts can be called. Now the requirement in my project is that a parent script calls a child script but this parent script has to be called through the Informatica tool. In Parent script I'm using TEMP=`getopt -o x:y: -l area:,volume:... (1 Reply)
Discussion started by: Panna
1 Replies
Eval::Closure(3)					User Contributed Perl Documentation					  Eval::Closure(3)

NAME
Eval::Closure - safely and cleanly create closures via string eval VERSION
version 0.11 SYNOPSIS
use Eval::Closure; my $code = eval_closure( source => 'sub { $foo++ }', environment => { '$foo' => 1, }, ); warn $code->(); # 1 warn $code->(); # 2 my $code2 = eval_closure( source => 'sub { $code->() }', ); # dies, $code isn't in scope DESCRIPTION
String eval is often used for dynamic code generation. For instance, "Moose" uses it heavily, to generate inlined versions of accessors and constructors, which speeds code up at runtime by a significant amount. String eval is not without its issues however - it's difficult to control the scope it's used in (which determines which variables are in scope inside the eval), and it's easy to miss compilation errors, since eval catches them and sticks them in $@ instead. This module attempts to solve these problems. It provides an "eval_closure" function, which evals a string in a clean environment, other than a fixed list of specified variables. Compilation errors are rethrown automatically. FUNCTIONS
eval_closure(%args) This function provides the main functionality of this module. It is exported by default. It takes a hash of parameters, with these keys being valid: source The string to be evaled. It should end by returning a code reference. It can access any variable declared in the "environment" parameter (and only those variables). It can be either a string, or an arrayref of lines (which will be joined with newlines to produce the string). environment The environment to provide to the eval. This should be a hashref, mapping variable names (including sigils) to references of the appropriate type. For instance, a valid value for environment would be "{ '@foo' => [] }" (which would allow the generated function to use an array named @foo). Generally, this is used to allow the generated function to access externally defined variables (so you would pass in a reference to a variable that already exists). In perl 5.18 and greater, the environment hash can contain variables with a sigil of "&". This will create a lexical sub in the evaluated code (see "The 'lexical_subs' feature" in feature). Using a "&" sigil on perl versions before lexical subs were available will throw an error. alias If set to true, the coderef returned closes over the variables referenced in the environment hashref. (This feature requires Devel::LexAlias.) If set to false, the coderef closes over a shallow copy of the variables. If this argument is omitted, Eval::Closure will currently assume false, but this assumption may change in a future version. description This lets you provide a bit more information in backtraces. Normally, when a function that was generated through string eval is called, that stack frame will show up as "(eval n)", where 'n' is a sequential identifier for every string eval that has happened so far in the program. Passing a "description" parameter lets you override that to something more useful (for instance, Moose overrides the description for accessors to something like "accessor foo at MyClass.pm, line 123"). line This lets you override the particular line number that appears in backtraces, much like the "description" option. The default is 1. terse_error Normally, this function appends the source code that failed to compile, and prepends some explanatory text. Setting this option to true suppresses that behavior so you get only the compilation error that Perl actually reported. BUGS
No known bugs. Please report any bugs to GitHub Issues at <https://github.com/doy/eval-closure/issues>. SEE ALSO
o Class::MOP::Method::Accessor This module is a factoring out of code that used to live here SUPPORT
You can find this documentation for this module with the perldoc command. perldoc Eval::Closure You can also look for information at: o MetaCPAN <https://metacpan.org/release/Eval-Closure> o Github <https://github.com/doy/eval-closure> o RT: CPAN's request tracker <http://rt.cpan.org/NoAuth/Bugs.html?Dist=Eval-Closure> o CPAN Ratings <http://cpanratings.perl.org/d/Eval-Closure> NOTES
Based on code from Class::MOP::Method::Accessor, by Stevan Little and the Moose Cabal. AUTHOR
Jesse Luehrs <doy@tozt.net> COPYRIGHT AND LICENSE
This software is copyright (c) 2013 by Jesse Luehrs. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. perl v5.18.2 2013-07-30 Eval::Closure(3)
All times are GMT -4. The time now is 06:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy