Samson Monaco Tutankhamen > Proc-Command > Proc::Command

Download:
Proc-Command-0.04.tar.gz

Dependencies

Annotate this POD

View/Report Bugs
Module Version: 1.05   Source  

NAME ^

Proc::Command - backtick that does not use the shell for Perl under Windows

SYNOPSIS ^

 use Proc::Command

 @reponse = Proc::Command->command($command)
 @reponse = Proc::Command->command($command, $trys)
 @reponse = Proc::Command->command($command, $trys, $sleep)

 use Proc::Command qw(command)

 @reponse = command($command)
 @reponse = command($command, $trys)
 @reponse = command($command, $trys, $sleep)

DESCRIPTION ^

Some Perls under Microsoft windows suffers disabilities over Unix Perls. One particular disability is a backtick without the console. Altough the Microsoft console, may be started without a window (start command with /b option or spawn program call), the Perl system command on windows usually creates a window. Creating a window causes immense user interface problem since it will randomly pop-up and take focus over the current window, erasing current entries into that window. Solutions such as "Proc::SafePipe" do not run on Perls for Window.

This module provides an answer by using the "open" command with a pipe to provide a backtick without a console that will run under Perls on Microsoft Windows.

REQUIREMENTS ^

Coming soon.

DEMONSTRATION ^

 ~~~~~~ Demonstration overview ~~~~~

Perl code begins with the prompt

 =>

The selected results from executing the Perl Code follow on the next lines. For example,

 => 2 + 2
 4

 ~~~~~~ The demonstration follows ~~~~~

 =>     use File::Spec;
 =>     use File::Package;
 =>     my $fp = 'File::Package';
 =>     my $loaded = '';
 =>  
 =>     my $pc = 'Proc::Command';
 =>     my ($command,$actual);
 => my $errors = $fp->load_package($pc)
 => $errors
 ''

 => $actual = $pc->command('echo hello')
 'hello
 '

QUALITY ASSURANCE ^

The module "t::Proc::Command" is the Software Test Description(STD) module for the "Proc::Command". module.

To generate all the test output files, run the generated test script, run the demonstration script and include it results in the "Proc::Command" POD, execute the following in any directory:

 tmake -test_verbose -replace -run  -pm=t::Proc::Command

Note that tmake.pl must be in the execution path $ENV{PATH} and the "t" directory containing "t::Proc::Command" on the same level as the "lib" directory that contains the "Proc::Command" module.

NOTES ^

AUTHOR

The holder of the copyright and maintainer is

<support@SoftwareDiamonds.com>

COPYRIGHT NOTICE

Copyrighted (c) 2002 Software Diamonds

All Rights Reserved

BINDING REQUIREMENTS NOTICE

Binding requirements are indexed with the pharse 'shall[dd]' where dd is an unique number for each header section. This conforms to standard federal government practices, 490A ("3.2.3.6" in STD490A). In accordance with the License, Software Diamonds is not liable for any requirement, binding or otherwise.

LICENSE

Software Diamonds permits the redistribution and use in source and binary forms, with or without modification, provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

SOFTWARE DIAMONDS, http::www.softwarediamonds.com, PROVIDES THIS SOFTWARE 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL SOFTWARE DIAMONDS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING USE OF THIS SOFTWARE, EVEN IF ADVISED OF NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE POSSIBILITY OF SUCH DAMAGE.

SEE_ALSO:

File::Spec
Proc::Command







syntax highlighting: