Motion: Some layered Photoshop files import as merged objects

2 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Print merged rows from two files by applying if condition

Hi all, I have list of two kind of files and I want to compare the rows and print the merged data by applying if condition. First kind of file looks like: and second kind of file looks like : I want to print the rows present in second file followed by 3 more columns from first...

2. UNIX for Dummies Questions & Answers

merged 10 files with column extraction into one

Hi, I have 600 text files. In each txt file, I have 3 columns, e.g: File 1 a 0.21 0.003 b 0.34 0.004 c 0.72 0.002 File 2 a 0.25 0.0083 b 0.38 0.0047 c 0.79 0.00234 File 3 a 0.45 0.0063 b 0.88 0.0027 c 0.29 0.00204 ... my filename as "sc2408_0_5278.txt sc2408_0_5279.txt...

LEARN ABOUT CENTOS

test::builder::module

Test::Builder::Module(3)				User Contributed Perl Documentation				  Test::Builder::Module(3)

NAME

       Test::Builder::Module - Base class for test modules

SYNOPSIS

	 # Emulates Test::Simple
	 package Your::Module;

	 my $CLASS = __PACKAGE__;

	 use base 'Test::Builder::Module';
	 @EXPORT = qw(ok);

	 sub ok ($;$) {
	     my $tb = $CLASS->builder;
	     return $tb->ok(@_);
	 }

	 1;

DESCRIPTION

       This is a superclass for Test::Builder-based modules.  It provides a handful of common functionality and a method of getting at the
       underlying Test::Builder object.

   Importing
       Test::Builder::Module is a subclass of Exporter which means your module is also a subclass of Exporter.	@EXPORT, @EXPORT_OK, etc...  all
       act normally.

       A few methods are provided to do the "use Your::Module tests =" 23> part for you.

       import

       Test::Builder::Module provides an import() method which acts in the same basic way as Test::More's, setting the plan and controlling
       exporting of functions and variables.  This allows your module to set the plan independent of Test::More.

       All arguments passed to import() are passed onto "Your::Module->builder->plan()" with the exception of "import =>[qw(things to import)]".

	   use Your::Module import => [qw(this that)], tests => 23;

       says to import the functions this() and that() as well as set the plan to be 23 tests.

       import() also sets the exported_to() attribute of your builder to be the caller of the import() function.

       Additional behaviors can be added to your import() method by overriding import_extra().

       import_extra

	   Your::Module->import_extra(@import_args);

       import_extra() is called by import().  It provides an opportunity for you to add behaviors to your module based on its import list.

       Any extra arguments which shouldn't be passed on to plan() should be stripped off by this method.

       See Test::More for an example of its use.

       NOTE This mechanism is VERY ALPHA AND LIKELY TO CHANGE as it feels like a bit of an ugly hack in its current form.

   Builder
       Test::Builder::Module provides some methods of getting at the underlying Test::Builder object.

       builder

	 my $builder = Your::Class->builder;

       This method returns the Test::Builder object associated with Your::Class.  It is not a constructor so you can call it as often as you like.

       This is the preferred way to get the Test::Builder object.  You should not get it via "Test::Builder->new" as was previously recommended.

       The object returned by builder() may change at runtime so you should call builder() inside each function rather than store it in a global.

	 sub ok {
	     my $builder = Your::Class->builder;

	     return $builder->ok(@_);
	 }

perl v5.16.3							    2011-02-23						  Test::Builder::Module(3)

OS X Support RSS