Sponsored Content
Top Forums Shell Programming and Scripting Can we use aliased commands in script? Post 95297 by Chanakya.m on Tuesday 10th of January 2006 04:25:59 AM
Old 01-10-2006
Can we use aliased commands in script?

Hi All,
I need a small help.. when we use aliased commands in shell script, they are not being recognized when I used. Is there any way to use aliased commands in scritping? Please let me know if u know...

Thank you
Chanu
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

calling a aliased variable

Issue: i have variable A which is an alias for variable B which is equal to "THIS IS A TEST" when every i echo variable A i only get the alias name for variable B, NOT the contents of variable B. HOSTNAME# echo $TESTIT + echo THIS IS A TEST THIS IS A TEST HOSTNAME# ls -l total... (10 Replies)
Discussion started by: Optimus_P
10 Replies

2. Shell Programming and Scripting

vi Commands in a Script

Perhaps there is a better way to do this, but right now this is all I can think of. If there is a better way to do this, all suggestions are welcome. I would like to take a file and perform the following actions on it. 1. Search for CREATE TABLE 2. Copy that line and paste it one line... (7 Replies)
Discussion started by: djschmitt
7 Replies

3. UNIX for Dummies Questions & Answers

script commands

my bad (2 Replies)
Discussion started by: romeoz
2 Replies

4. Shell Programming and Scripting

Repeating commands in a script

I have written a script that I want to be repeated. The script that I wrote outputs the date, how many people are on the system, how many people logged in before me, and how many people logged in after me. Than what I want it to do is after it outputs the 4 lines I want it to go back to the... (4 Replies)
Discussion started by: Dave2874
4 Replies

5. Shell Programming and Scripting

running commands from script

I'm new to unix and I have a fairly simple problem: Lets say I am in a specific directory and I run the command: "dirs" , I get an output of all the folders that i pushed into the stack (as expected), buut, when when I create a script (called test): #! /bin/csh dirs and then i run:... (2 Replies)
Discussion started by: owijust
2 Replies

6. Shell Programming and Scripting

How to make a script out of commands

Hi, I have a very basic knowledge of Unix and I need your help for a small script that will do the following commands that I do manually by just giving the filename TPR20080414.txt cut -d'|' -f3,4 TPR20080414.txt> oe_012.lkp awk -F "|" '{temp=$1;$1=$2;$2=temp}1' OFS="|" oe_012.lkp >... (3 Replies)
Discussion started by: sickboy
3 Replies

7. Shell Programming and Scripting

Commands in background in a script

Hi, I was writing a script for backup,however i stumbled upon this.( As i mentioned in my earlier posts iam a beginner in shell scripting). Here is a piece of code case $DB_STAT in OFFLINE) echo "Service $SID currently $DB_STAT" ... (1 Reply)
Discussion started by: maverick_here
1 Replies

8. Shell Programming and Scripting

Issue commands within script

What is the best way of having a script that has it's own commands, which can be called at any stage in the script. I'm sure there is a technical term for this type of CLI app which can help my search but I can't remember it. Is using trap the best way of doing this. (6 Replies)
Discussion started by: cue
6 Replies

9. UNIX for Dummies Questions & Answers

UNIX commands for a script that I need

Hello. I need help trying to create a script in UNIX to do the following steps. I don't know which commands to input to achieve this. 1. In a directory tree, I want to duplicate all .txt files into the same directory, so 2 of each file exists in each directory where there is a .txt file ... (4 Replies)
Discussion started by: TitanTlaloc
4 Replies

10. Shell Programming and Scripting

Using commands within bash script

The purpose of enclosed script is to execute selected command and output success or failure in whiptail msgBox Works as expected when command returns zero to msgBox. I cannot figure out how to continue / automate my script when command expects reply to continue / terminate. I am doing it... (2 Replies)
Discussion started by: annacreek
2 Replies
aliased(3)						User Contributed Perl Documentation						aliased(3)

NAME
aliased - Use shorter versions of class names. VERSION
0.31 SYNOPSIS
# Class name interface use aliased 'My::Company::Namespace::Customer'; my $cust = Customer->new; use aliased 'My::Company::Namespace::Preferred::Customer' => 'Preferred'; my $pref = Preferred->new; # Variable interface use aliased; my $Customer = alias "My::Other::Namespace::Customer"; my $cust = $Customer->new; my $Preferred = alias "My::Other::Namespace::Preferred::Customer"; my $pref = $Preferred->new; DESCRIPTION
"aliased" is simple in concept but is a rather handy module. It loads the class you specify and exports into your namespace a subroutine that returns the class name. You can explicitly alias the class to another name or, if you prefer, you can do so implicitly. In the latter case, the name of the subroutine is the last part of the class name. Thus, it does something similar to the following: #use aliased 'Some::Annoyingly::Long::Module::Name::Customer'; use Some::Annoyingly::Long::Module::Name::Customer; sub Customer { return 'Some::Annoyingly::Long::Module::Name::Customer'; } my $cust = Customer->new; This module is useful if you prefer a shorter name for a class. It's also handy if a class has been renamed. (Some may object to the term "aliasing" because we're not aliasing one namespace to another, but it's a handy term. Just keep in mind that this is done with a subroutine and not with typeglobs and weird namespace munging.) Note that this is only for "use"ing OO modules. You cannot use this to load procedural modules. See the Why OO Only? section. Also, don't let the version number fool you. This code is ridiculously simple and is just fine for most use. Implicit Aliasing The most common use of this module is: use aliased 'Some::Module::name'; "aliased" will allow you to reference the class by the last part of the class name. Thus, "Really::Long::Name" becomes "Name". It does this by exporting a subroutine into your namespace with the same name as the aliased name. This subroutine returns the original class name. For example: use aliased "Acme::Company::Customer"; my $cust = Customer->find($id); Note that any class method can be called on the shorter version of the class name, not just the constructor. Explicit Aliasing Sometimes two class names can cause a conflict (they both end with "Customer" for example), or you already have a subroutine with the same name as the aliased name. In that case, you can make an explicit alias by stating the name you wish to alias to: use aliased 'Original::Module::Name' => 'NewName'; Here's how we use "aliased" to avoid conflicts: use aliased "Really::Long::Name"; use aliased "Another::Really::Long::Name" => "Aname"; my $name = Name->new; my $aname = Aname->new; You can even alias to a different package: use aliased "Another::Really::Long::Name" => "Another::Name"; my $aname = Another::Name->new; Messing around with different namespaces is a really bad idea and you probably don't want to do this. However, it might prove handy if the module you are using has been renamed. If the interface has not changed, this allows you to use the new module by only changing one line of code. use aliased "New::Module::Name" => "Old::Module::Name"; my $thing = Old::Module::Name->new; Import Lists Sometimes, even with an OO module, you need to specify extra arguments when using the module. When this happens, simply use "Explicit Aliasing" followed by the import list: Snippet 1: use Some::Module::Name qw/foo bar/; my $o = Some::Module::Name->some_class_method; Snippet 2 (equivalent to snippet 1): use aliased 'Some::Module::Name' => 'Name', qw/foo bar/; my $o = Name->some_class_method; Note: remember, you cannot use import lists with "Implicit Aliasing". As a result, you may simply prefer to only use "Explicit Aliasing" as a matter of style. alias() This function is only exported if you specify "use aliased" with no import list. use aliased; my $alias = alias($class); my $alias = alias($class, @imports); alias() is an alternative to "use aliased ..." which uses less magic and avoids some of the ambiguities. Like "use aliased" it "use"s the $class (pass in @imports, if given) but instead of providing an "Alias" constant it simply returns a scalar set to the $class name. my $thing = alias("Some::Thing::With::A::Long::Name"); # Just like Some::Thing::With::A::Long::Name->method $thing->method; The use of a scalar instead of a constant avoids any possible ambiguity when aliasing two similar names: # No ambiguity despite the fact that they both end with "Name" my $thing = alias("Some::Thing::With::A::Long::Name"); my $other = alias("Some::Other::Thing::With::A::Long::Name"); and there is no magic constant exported into your namespace. The only caveat is loading of the $class happens at run time. If $class exports anything you might want to ensure it is loaded at compile time with: my $thing; BEGIN { $thing = alias("Some::Thing"); } However, since OO classes rarely export this should not be necessary. prefix() (experimental) This function is only exported if you specify "use aliased" with no import list. use aliased; Sometimes you find you have a ton of packages in the same top-level namespace and you want to alias them, but only use them on demand. For example: # instead of: MailVerwaltung::Client::Exception::REST::Response->throw() my $error = prefix('MailVerwaltung::Client::Exception'); $error->('REST::Response')->throw(); # same as above $error->()->throw; # same as MailVerwaltung::Client::Exception->throw Why OO Only? Some people have asked why this code only support object-oriented modules (OO). If I were to support normal subroutines, I would have to allow the following syntax: use aliased 'Some::Really::Long::Module::Name'; my $data = Name::data(); That causes a serious problem. The only (reasonable) way it can be done is to handle the aliasing via typeglobs. Thus, instead of a subroutine that provides the class name, we alias one package to another (as the namespace module does.) However, we really don't want to simply alias one package to another and wipe out namespaces willy-nilly. By merely exporting a single subroutine to a namespace, we minimize the issue. Fortunately, this doesn't seem to be that much of a problem. Non-OO modules generally support exporting of the functions you need and this eliminates the need for a module such as this. EXPORT
This modules exports a subroutine with the same name as the "aliased" name. BUGS
There are no known bugs in this module, but feel free to email me reports. SEE ALSO
The namespace module. THANKS
Many thanks to Rentrak, Inc. (http://www.rentrak.com/) for graciously allowing me to replicate the functionality of some of their internal code. AUTHOR
Curtis Poe, "ovid [at] cpan [dot] org" COPYRIGHT AND LICENSE
Copyright (C) 2005 by Curtis "Ovid" Poe This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself, either Perl version 5.8.5 or, at your option, any later version of Perl 5 you may have available. perl v5.18.2 2017-10-06 aliased(3)
All times are GMT -4. The time now is 06:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy