Sponsored Content
Full Discussion: Perl Methods Calling
Top Forums Shell Programming and Scripting Perl Methods Calling Post 302792921 by elixir_sinari on Thursday 11th of April 2013 10:33:13 AM
Old 04-11-2013
Quote:
Originally Posted by adisky123
Can you please explain how this works
Code:
$this = {'a' =>shift,'b'=>shift,'c'=>shift};

That is evaluating 'a' =>shift,'b'=>shift,'c'=>shift in list context, storing it in an anonymous hash, and returning a reference to this hash (through the anonymous hash composer/constructor {}) to be assigned later to the scalar variable $this.

=> is just a fancy comma. The 3 shifts get the arguments passed to the class' constructor new in that order. That is, first argument will be associated with key a, second with key b, and so on. If no arguments are passed to the constructor (apart from the default class name or object reference, if invoked as a method), the corresponding keys' values will be undef.

By the way, your Perl skills are less than wonderful. There are a lot of questionable/wrong things in your code. E.g., returning 1 in the module file at the wrong place, multiple lexical declarations with the same symbol and type in the same lexical scope, etc.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

URL calling in PERL

All Please help me to call url in Perl. Ex: http://www.test.com/dynf?urn=123 Assume it will return success if 123 is in urn or it will return " failed". I want store this return type in a variable. Please help me to call the URL through PERL. Thanx in advance Regards Deepak (1 Reply)
Discussion started by: DeepakXavier
1 Replies

2. Shell Programming and Scripting

calling a shell script from perl

Hi all, Not sure if this is the right forum to post query regarding perl script. I have a perl script which internally calls a shell script. My problem is that the shell script should be passed command line arguments. I call a shell script from perl using: system("sript.sh"); How do... (3 Replies)
Discussion started by: gurukottur
3 Replies

3. Shell Programming and Scripting

Calling Winzip from perl script

Hi, I would like to invoke "Winzip" utility from a perl script, input the name of zip file and provide output path for unzipped files. Any pointers will be appreciated. Thanks (5 Replies)
Discussion started by: MobileUser
5 Replies

4. Programming

calling Perl from C

Hi, I am trying to execute a perl script from c program. I tried using system command. system("perl test.pl filename") ; This perl program takes filename as input and prints a number to screen. I need to get that returned number in C program. system command is... (3 Replies)
Discussion started by: pkusumam
3 Replies

5. Shell Programming and Scripting

calling problem in perl script

Hi , Here is my piece of code-- main(); sub main { $result = GetOptions ("LogDir=s" => \$LogDir, "Summary" => \$Summary, "Indiviual=s" => \$Individual , "Diagnostics=s" => \$Diagnostics, ... (1 Reply)
Discussion started by: namishtiwari
1 Replies

6. UNIX for Dummies Questions & Answers

Calling a c program using perl script

On bash I run precompiled c Program as follows: ./create_cust 1 10000 US S > us_cust.csv create_cust is a c program and requires 4 parameters. I am redirecting the output of this program to csv file I need to run this same program in perl I am aware of exec command though not... (7 Replies)
Discussion started by: gkbond
7 Replies

7. Shell Programming and Scripting

Calling 3 perl script from one

hi all, I have 3 perl scripts a.pl,b.pl and c.pl each of these work when i pass a date for eg: perl c.pl 2010-05-27 now i want to write a perl script that would call the 3 scripts and make it run all the 3 scripts (a.pl,b.pl,c.pl) parallelly rather than 1 after the other....... pls... (2 Replies)
Discussion started by: siva_nagarajan
2 Replies

8. Shell Programming and Scripting

calling perl subroutine from perl expect module

All, Is it possible to call a subroutine from the perl expect module after logging to a system that is within the same program. My situation is I need to run a logic inside a machine that I'm logging in using the expect module, the logic is also available in the same expect program. Thanks,... (5 Replies)
Discussion started by: arun_maffy
5 Replies

9. Shell Programming and Scripting

Methods to SSH (Perl)...

Can anyone break down the different methods of using SSH in perl? I'm currently using Net::SSH::Expect, which allows me to login to a machine and execute multiple commands without having to ssh again. This feature of holding the session works well for me, but it's slow. If I set timeouts to 4... (3 Replies)
Discussion started by: mrwatkin
3 Replies

10. Shell Programming and Scripting

Methods For Debugging Perl Problems

Note: Not a programmer by profession but occasionally have to program. I am looking for general methods and freely/readily available tools employed to debug problems during development of perl scripts. Anything that has really helped you out with problems you just couldn't find. A couple of... (5 Replies)
Discussion started by: Vi-Curious
5 Replies
Moose::Manual::Construction(3pm)			User Contributed Perl Documentation			  Moose::Manual::Construction(3pm)

NAME
Moose::Manual::Construction - Object construction (and destruction) with Moose VERSION
version 2.0603 WHERE'S THE CONSTRUCTOR? Do not define a "new()" method for your classes! When you "use Moose" in your class, your class becomes a subclass of Moose::Object. The Moose::Object provides a "new()" method for your class. If you follow our recommendations in Moose::Manual::BestPractices and make your class immutable, then you actually get a class- specific "new()" method "inlined" in your class. OBJECT CONSTRUCTION AND ATTRIBUTES
The Moose-provided constructor accepts a hash or hash reference of named parameters matching your attributes (actually, matching their "init_arg"s). This is just another way in which Moose keeps you from worrying how classes are implemented. Simply define a class and you're ready to start creating objects! OBJECT CONSTRUCTION HOOKS
Moose lets you hook into object construction. You can validate an object's state, do logging, customize construction from parameters which do not match your attributes, or maybe allow non-hash(ref) constructor arguments. You can do this by creating "BUILD" and/or "BUILDARGS" methods. If these methods exist in your class, Moose will arrange for them to be called as part of the object construction process. BUILDARGS The "BUILDARGS" method is called as a class method before an object is created. It will receive all of the arguments that were passed to "new()" as-is, and is expected to return a hash reference. This hash reference will be used to construct the object, so it should contain keys matching your attributes' names (well, "init_arg"s). One common use for "BUILDARGS" is to accommodate a non-hash(ref) calling style. For example, we might want to allow our Person class to be called with a single argument of a social security number, "Person->new($ssn)". Without a "BUILDARGS" method, Moose will complain, because it expects a hash or hash reference. We can use the "BUILDARGS" method to accommodate this calling style: around BUILDARGS => sub { my $orig = shift; my $class = shift; if ( @_ == 1 && !ref $_[0] ) { return $class->$orig( ssn => $_[0] ); } else { return $class->$orig(@_); } }; Note the call to "$class->$orig". This will call the default "BUILDARGS" in Moose::Object. This method takes care of distinguishing between a hash reference and a plain hash for you. BUILD The "BUILD" method is called after an object is created. There are several reasons to use a "BUILD" method. One of the most common is to check that the object state is valid. While we can validate individual attributes through the use of types, we can't validate the state of a whole object that way. sub BUILD { my $self = shift; if ( $self->country_of_residence eq 'USA' ) { die 'All US residents must have an SSN' unless $self->has_ssn; } } Another use of a "BUILD" method could be for logging or tracking object creation. sub BUILD { my $self = shift; debug( 'Made a new person - SSN = ', $self->ssn, ); } The "BUILD" method is called with the hash reference of the parameters passed to the constructor (after munging by "BUILDARGS"). This gives you a chance to do something with parameters that do not represent object attributes. sub BUILD { my $self = shift; my $args = shift; $self->add_friend( My::User->new( user_id => $args->{user_id}, ) ); } BUILD and parent classes The interaction between multiple "BUILD" methods in an inheritance hierarchy is different from normal Perl methods. You should never call "$self->SUPER::BUILD", nor should you ever apply a method modifier to "BUILD". Moose arranges to have all of the "BUILD" methods in a hierarchy called when an object is constructed, from parents to children. This might be surprising at first, because it reverses the normal order of method inheritance. The theory behind this is that "BUILD" methods can only be used for increasing specialization of a class's constraints, so it makes sense to call the least specific "BUILD" method first. Also, this is how Perl 6 does it. OBJECT DESTRUCTION
Moose provides a hook for object destruction with the "DEMOLISH" method. As with "BUILD", you should never explicitly call "$self->SUPER::DEMOLISH". Moose will arrange for all of the "DEMOLISH" methods in your hierarchy to be called, from most to least specific. Each "DEMOLISH" method is called with a single argument. In most cases, Perl's built-in garbage collection is sufficient, and you won't need to provide a "DEMOLISH" method. Error Handling During Destruction The interaction of object destruction and Perl's global $@ and $? variables can be very confusing. Moose always localizes $? when an object is being destroyed. This means that if you explicitly call "exit", that exit code will be preserved even if an object's destructor makes a system call. Moose also preserves $@ against any "eval" calls that may happen during object destruction. However, if an object's "DEMOLISH" method actually dies, Moose explicitly rethrows that error. If you do not like this behavior, you will have to provide your own "DESTROY" method and use that instead of the one provided by Moose::Object. You can do this to preserve $@ and capture any errors from object destruction by creating an error stack. AUTHOR
Moose is maintained by the Moose Cabal, along with the help of many contributors. See "CABAL" in Moose and "CONTRIBUTORS" in Moose for details. COPYRIGHT AND LICENSE
This software is copyright (c) 2012 by Infinity Interactive, Inc.. 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.14.2 2012-06-28 Moose::Manual::Construction(3pm)
All times are GMT -4. The time now is 06:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy