6.1.2
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 7
Pandore 6.1.2
Pandora is a standardized library of image processing functions. more>>
The current version contains functions for 1D, 2D, and 3D images, which may be greyscale, color, or multispectral.
Enhancements:
- A limitation in SaveData and LoadData that restricted the size of data has been fixed.
- There are assorted other minor bugfixes.
<<lessEnhancements:
- A limitation in SaveData and LoadData that restricted the size of data has been fixed.
- There are assorted other minor bugfixes.
Download (MB)
Added: 2007-06-04 License: CeCILL (CeCILL Free Software License Agreement) Price:
872 downloads
Sort::Key 1.28
Sort::Key is the fastest way to sort anything in Perl. more>>
Sort::Key is the fastest way to sort anything in Perl.
SYNOPSIS
use Sort::Key qw(keysort nkeysort ikeysort);
@by_name = keysort { "$_->{surname} $_->{name}" } @people;
# sorting by a numeric key:
@by_age = nkeysort { $_->{age} } @people;
# sorting by a numeric integer key:
@by_sons = ikeysort { $_->{sons} } @people;
Sort::Key provides a set of functions to sort lists of values by some calculated key value.
It is faster (usually much faster) and uses less memory than other alternatives implemented around perl sort function (ST, GRT, etc.).
Multikey sorting functionality is also provided via the companion modules Sort::Key::Multi, Sort::Key::Maker and Sort::Key::Register.
FUNCTIONS
This module provides a large number of sorting subroutines but they are all variations off the keysort one:
@sorted = keysort { CALC_KEY($_) } @data
that is conceptually equivalent to
@sorted = sort { CALC_KEY($a) cmp CALC_KEY($b) } @data
and where CALC_KEY($_) can be any expresion to extract the key value from $_ (not only a subroutine call).
For instance, some variations are nkeysort that performs a numeric comparison, rkeysort that orders the data in descending order, ikeysort and ukeysort that are optimized versions of nkeysort that can be used when the keys are integers or unsigned integers respectively, etc.
Also, inplace versions of the sorters are provided. For instance
keysort_inplace { CALC_KEY($_) } @data
that is equivalent to
@data = keysort { CALC_KEY($_) } @data
but being (a bit) faster and using less memory.
The full list of subroutines that can be imported from this module follows:
keysort { CALC_KEY } @array
returns the elements on @array sorted by the key calculated applying { CALC_KEY } to them.
Inside { CALC_KEY }, the object is available as $_.
For example:
@a=({name=>john, surname=>smith}, {name=>paul, surname=>belvedere});
@by_name=keysort {$_->{name}} @a;
This function honours the use locale pragma.
nkeysort { CALC_KEY } @array
similar to keysort but compares the keys numerically instead of as strings.
This function honours the use integer pragma, i.e.:
use integer;
my @s=(2.4, 2.0, 1.6, 1.2, 0.8);
my @ns = nkeysort { $_ } @s;
print "@nsn"
prints
0.8 1.6 1.2 2.4 2
rnkeysort { CALC_KEY } @array
works as nkeysort, comparing keys in reverse (or descending) numerical order.
ikeysort { CALC_KEY } @array
works as keysort but compares the keys as integers (32 bits or more, no checking is performed for overflows).
rikeysort { CALC_KEY } @array
works as ikeysort, but in reverse (or descending) order.
ukeysort { CALC_KEY } @array
works as keysort but compares the keys as unsigned integers (32 bits or more).
For instance, it can be used to efficiently sort IP4 addresses:
my @data = qw(1.2.3.4 4.3.2.1 11.1.111.1 222.12.1.34
0.0.0.0 255.255.255.0) 127.0.0.1);
my @sorted = ukeysort {
my @a = split /./;
(((($a[0] name,
$_->middlename },
qw(str str str);
Sort::Key::register_type Color =>
sub { $_->R, $_->G, $_->B },
qw(int int int);
Once a datatype has been registered it can be used in the same way as types supported natively, even for defining new types, i.e.:
Sort::Key::register_type Family =>
sub { $_->man, $_->woman },
qw(Person Person);
<<lessSYNOPSIS
use Sort::Key qw(keysort nkeysort ikeysort);
@by_name = keysort { "$_->{surname} $_->{name}" } @people;
# sorting by a numeric key:
@by_age = nkeysort { $_->{age} } @people;
# sorting by a numeric integer key:
@by_sons = ikeysort { $_->{sons} } @people;
Sort::Key provides a set of functions to sort lists of values by some calculated key value.
It is faster (usually much faster) and uses less memory than other alternatives implemented around perl sort function (ST, GRT, etc.).
Multikey sorting functionality is also provided via the companion modules Sort::Key::Multi, Sort::Key::Maker and Sort::Key::Register.
FUNCTIONS
This module provides a large number of sorting subroutines but they are all variations off the keysort one:
@sorted = keysort { CALC_KEY($_) } @data
that is conceptually equivalent to
@sorted = sort { CALC_KEY($a) cmp CALC_KEY($b) } @data
and where CALC_KEY($_) can be any expresion to extract the key value from $_ (not only a subroutine call).
For instance, some variations are nkeysort that performs a numeric comparison, rkeysort that orders the data in descending order, ikeysort and ukeysort that are optimized versions of nkeysort that can be used when the keys are integers or unsigned integers respectively, etc.
Also, inplace versions of the sorters are provided. For instance
keysort_inplace { CALC_KEY($_) } @data
that is equivalent to
@data = keysort { CALC_KEY($_) } @data
but being (a bit) faster and using less memory.
The full list of subroutines that can be imported from this module follows:
keysort { CALC_KEY } @array
returns the elements on @array sorted by the key calculated applying { CALC_KEY } to them.
Inside { CALC_KEY }, the object is available as $_.
For example:
@a=({name=>john, surname=>smith}, {name=>paul, surname=>belvedere});
@by_name=keysort {$_->{name}} @a;
This function honours the use locale pragma.
nkeysort { CALC_KEY } @array
similar to keysort but compares the keys numerically instead of as strings.
This function honours the use integer pragma, i.e.:
use integer;
my @s=(2.4, 2.0, 1.6, 1.2, 0.8);
my @ns = nkeysort { $_ } @s;
print "@nsn"
prints
0.8 1.6 1.2 2.4 2
rnkeysort { CALC_KEY } @array
works as nkeysort, comparing keys in reverse (or descending) numerical order.
ikeysort { CALC_KEY } @array
works as keysort but compares the keys as integers (32 bits or more, no checking is performed for overflows).
rikeysort { CALC_KEY } @array
works as ikeysort, but in reverse (or descending) order.
ukeysort { CALC_KEY } @array
works as keysort but compares the keys as unsigned integers (32 bits or more).
For instance, it can be used to efficiently sort IP4 addresses:
my @data = qw(1.2.3.4 4.3.2.1 11.1.111.1 222.12.1.34
0.0.0.0 255.255.255.0) 127.0.0.1);
my @sorted = ukeysort {
my @a = split /./;
(((($a[0] name,
$_->middlename },
qw(str str str);
Sort::Key::register_type Color =>
sub { $_->R, $_->G, $_->B },
qw(int int int);
Once a datatype has been registered it can be used in the same way as types supported natively, even for defining new types, i.e.:
Sort::Key::register_type Family =>
sub { $_->man, $_->woman },
qw(Person Person);
Download (0.055MB)
Added: 2007-05-22 License: Perl Artistic License Price:
888 downloads
Apache::TestUtil 1.29
Apache::TestUtil Perl module contains utility functions for writing tests. more>>
Apache::TestUtil Perl module contains utility functions for writing tests.
SYNOPSIS
use Apache::Test;
use Apache::TestUtil;
ok t_cmp("foo", "foo", "sanity check");
t_write_file("filename", @content);
my $fh = t_open_file($filename);
t_mkdir("/foo/bar");
t_rmtree("/foo/bar");
t_is_equal($a, $b);
Apache::TestUtil automatically exports a number of functions useful in writing tests.
All the files and directories created using the functions from this package will be automatically destroyed at the end of the program execution (via END block). You should not use these functions other than from within tests which should cleanup all the created directories and files at the end of the test.
FUNCTIONS
t_cmp()
t_cmp($received, $expected, $comment);
t_cmp() prints the values of $comment, $expected and $received. e.g.:
t_cmp(1, 1, "1 == 1?");
prints:
# testing : 1 == 1?
# expected: 1
# received: 1
then it returns the result of comparison of the $expected and the $received variables. Usually, the return value of this function is fed directly to the ok() function, like this:
ok t_cmp(1, 1, "1 == 1?");
the third argument ($comment) is optional, mostly useful for telling what the comparison is trying to do.
It is valid to use undef as an expected value. Therefore:
my $foo;
t_cmp(undef, $foo, "undef == undef?");
will return a true value.
You can compare any two data-structures with t_cmp(). Just make sure that if you pass non-scalars, you have to pass their references. The datastructures can be deeply nested. For example you can compare:
t_cmp({1 => [2..3,{5..8}], 4 => [5..6]},
{1 => [2..3,{5..8}], 4 => [5..6]},
"hash of array of hashes");
You can also compare the second argument against the first as a regex. Use the qr// function in the second argument. For example:
t_cmp("abcd", qr/^abc/, "regex compare");
will do:
"abcd" =~ /^abc/;
This function is exported by default.
t_filepath_cmp()
This function is used to compare two filepaths via t_cmp(). For non-Win32, it simply uses t_cmp() for the comparison, but for Win32, Win32::GetLongPathName() is invoked to convert the first two arguments to their DOS long pathname. This is useful when there is a possibility the two paths being compared are not both represented by their long or short pathname.
This function is exported by default.
t_debug()
t_debug("testing feature foo");
t_debug("test", [1..3], 5, {a=>[1..5]});
t_debug() prints out any datastructure while prepending # at the beginning of each line, to make the debug printouts comply with Test::Harnesss requirements. This function should be always used for debug prints, since if in the future the debug printing will change (e.g. redirected into a file) your tests wont need to be changed.
the special global variable $Apache::TestUtil::DEBUG_OUTPUT can be used to redirect the output from t_debug() and related calls such as t_write_file(). for example, from a server-side test you would probably need to redirect it to STDERR:
sub handler {
plan $r, tests => 1;
local $Apache::TestUtil::DEBUG_OUTPUT = *STDERR;
t_write_file(/tmp/foo, bar);
...
}
left to its own devices, t_debug() will collide with the standard HTTP protocol during server-side tests, resulting in a situation both confusing difficult to debug. but STDOUT is left as the default, since you probably dont want debug output under normal circumstances unless running under verbose mode.
This function is exported by default.
t_write_file()
t_write_file($filename, @lines);
t_write_file() creates a new file at $filename or overwrites the existing file with the content passed in @lines. If only the $filename is passed, an empty file will be created.
If parent directories of $filename dont exist they will be automagically created.
The generated file will be automatically deleted at the end of the programs execution.
This function is exported by default.
t_append_file()
t_append_file($filename, @lines);
t_append_file() is similar to t_write_file(), but it doesnt clobber existing files and appends @lines to the end of the file. If the file doesnt exist it will create it.
If parent directories of $filename dont exist they will be automagically created.
The generated file will be registered to be automatically deleted at the end of the programs execution, only if the file was created by t_append_file().
This function is exported by default.
t_write_shell_script()
Apache::TestUtil::t_write_shell_script($filename, @lines);
Similar to t_write_file() but creates a portable shell/batch script. The created filename is constructed from $filename and an appropriate extension automatically selected according to the platform the code is running under.
It returns the extension of the created file.
t_write_perl_script()
Apache::TestUtil::t_write_perl_script($filename, @lines);
Similar to t_write_file() but creates a executable Perl script with correctly set shebang line.
t_open_file()
my $fh = t_open_file($filename);
t_open_file() opens a file $filename for writing and returns the file handle to the opened file.
If parent directories of $filename dont exist they will be automagically created.
The generated file will be automatically deleted at the end of the programs execution.
This function is exported by default.
t_mkdir()
t_mkdir($dirname);
t_mkdir() creates a directory $dirname. The operation will fail if the parent directory doesnt exist.
If parent directories of $dirname dont exist they will be automagically created.
The generated directory will be automatically deleted at the end of the programs execution.
This function is exported by default.
t_rmtree()
t_rmtree(@dirs);
t_rmtree() deletes the whole directories trees passed in @dirs.
This function is exported by default.
t_chown()
Apache::TestUtil::t_chown($file);
Change ownership of $file to the tests User/Group. This function is noop on platforms where chown(2) is unsupported (e.g. Win32).
t_is_equal()
t_is_equal($a, $b);
t_is_equal() compares any two datastructures and returns 1 if they are exactly the same, otherwise 0. The datastructures can be nested hashes, arrays, scalars, undefs or a combination of any of these. See t_cmp() for an example.
If $b is a regex reference, the regex comparison $a =~ $b is performed. For example:
t_is_equal($server_version, qr{^Apache});
If comparing non-scalars make sure to pass the references to the datastructures.
This function is exported by default.
t_server_log_error_is_expected()
If the handlers execution results in an error or a warning logged to the error_log file which is expected, its a good idea to have a disclaimer printed before the error itself, so one can tell real problems with tests from expected errors. For example when testing how the package behaves under error conditions the error_log file might be loaded with errors, most of which are expected.
For example if a handler is about to generate a run-time error, this function can be used as:
use Apache::TestUtil;
...
sub handler {
my $r = shift;
...
t_server_log_error_is_expected();
die "failed because ...";
}
After running this handler the error_log file will include:
*** The following error entry is expected and harmless ***
[Tue Apr 01 14:00:21 2003] [error] failed because ...
When more than one entry is expected, an optional numerical argument, indicating how many entries to expect, can be passed. For example:
t_server_log_error_is_expected(2);
will generate:
*** The following 2 error entries are expected and harmless ***
If the error is generated at compile time, the logging must be done in the BEGIN block at the very beginning of the file:
BEGIN {
use Apache::TestUtil;
t_server_log_error_is_expected();
}
use DOES_NOT_exist;
After attempting to run this handler the error_log file will include:
*** The following error entry is expected and harmless ***
[Tue Apr 01 14:04:49 2003] [error] Cant locate "DOES_NOT_exist.pm"
in @INC (@INC contains: ...
Also see t_server_log_warn_is_expected() which is similar but used for warnings.
This function is exported by default.
t_server_log_warn_is_expected()
t_server_log_warn_is_expected() generates a disclaimer for expected warnings.
See the explanation for t_server_log_error_is_expected() for more details.
This function is exported by default.
t_client_log_error_is_expected()
t_client_log_error_is_expected() generates a disclaimer for expected errors. But in contrast to t_server_log_error_is_expected() called by the client side of the script.
See the explanation for t_server_log_error_is_expected() for more details.
For example the following client script fails to find the handler:
use Apache::Test;
use Apache::TestUtil;
use Apache::TestRequest qw(GET);
plan tests => 1;
t_client_log_error_is_expected();
my $url = "/error_document/cannot_be_found";
my $res = GET($url);
ok t_cmp(404, $res->code, "test 404");
After running this test the error_log file will include an entry similar to the following snippet:
*** The following error entry is expected and harmless ***
[Tue Apr 01 14:02:55 2003] [error] [client 127.0.0.1]
File does not exist: /tmp/test/t/htdocs/error
When more than one entry is expected, an optional numerical argument, indicating how many entries to expect, can be passed. For example:
t_client_log_error_is_expected(2);
will generate:
*** The following 2 error entries are expected and harmless ***
This function is exported by default.
t_client_log_warn_is_expected()
t_client_log_warn_is_expected() generates a disclaimer for expected warnings on the client side.
See the explanation for t_client_log_error_is_expected() for more details.
This function is exported by default.
t_catfile(a, b, c)
This function is essentially File::Spec->catfile, but on Win32 will use Win32::GetLongpathName() to convert the result to a long path name (if the result is an absolute file). The function is not exported by default.
t_catfile_apache(a, b, c)
This function is essentially File::Spec::Unix->catfile, but on Win32 will use Win32::GetLongpathName() to convert the result to a long path name (if the result is an absolute file). It is useful when comparing something to that returned by Apache, which uses a Unix-style specification with forward slashes for directory separators. The function is not exported by default.
t_start_error_log_watch(), t_finish_error_log_watch()
This pair of functions provides an easy interface for checking the presence or absense of any particular message or messages in the httpd error_log that were generated by the httpd daemon as part of a test suite. It is likely, that you should proceed this with a call to one of the t_*_is_expected() functions.
t_start_error_log_watch();
do_it;
ok grep {...} t_finish_error_log_watch()
<<lessSYNOPSIS
use Apache::Test;
use Apache::TestUtil;
ok t_cmp("foo", "foo", "sanity check");
t_write_file("filename", @content);
my $fh = t_open_file($filename);
t_mkdir("/foo/bar");
t_rmtree("/foo/bar");
t_is_equal($a, $b);
Apache::TestUtil automatically exports a number of functions useful in writing tests.
All the files and directories created using the functions from this package will be automatically destroyed at the end of the program execution (via END block). You should not use these functions other than from within tests which should cleanup all the created directories and files at the end of the test.
FUNCTIONS
t_cmp()
t_cmp($received, $expected, $comment);
t_cmp() prints the values of $comment, $expected and $received. e.g.:
t_cmp(1, 1, "1 == 1?");
prints:
# testing : 1 == 1?
# expected: 1
# received: 1
then it returns the result of comparison of the $expected and the $received variables. Usually, the return value of this function is fed directly to the ok() function, like this:
ok t_cmp(1, 1, "1 == 1?");
the third argument ($comment) is optional, mostly useful for telling what the comparison is trying to do.
It is valid to use undef as an expected value. Therefore:
my $foo;
t_cmp(undef, $foo, "undef == undef?");
will return a true value.
You can compare any two data-structures with t_cmp(). Just make sure that if you pass non-scalars, you have to pass their references. The datastructures can be deeply nested. For example you can compare:
t_cmp({1 => [2..3,{5..8}], 4 => [5..6]},
{1 => [2..3,{5..8}], 4 => [5..6]},
"hash of array of hashes");
You can also compare the second argument against the first as a regex. Use the qr// function in the second argument. For example:
t_cmp("abcd", qr/^abc/, "regex compare");
will do:
"abcd" =~ /^abc/;
This function is exported by default.
t_filepath_cmp()
This function is used to compare two filepaths via t_cmp(). For non-Win32, it simply uses t_cmp() for the comparison, but for Win32, Win32::GetLongPathName() is invoked to convert the first two arguments to their DOS long pathname. This is useful when there is a possibility the two paths being compared are not both represented by their long or short pathname.
This function is exported by default.
t_debug()
t_debug("testing feature foo");
t_debug("test", [1..3], 5, {a=>[1..5]});
t_debug() prints out any datastructure while prepending # at the beginning of each line, to make the debug printouts comply with Test::Harnesss requirements. This function should be always used for debug prints, since if in the future the debug printing will change (e.g. redirected into a file) your tests wont need to be changed.
the special global variable $Apache::TestUtil::DEBUG_OUTPUT can be used to redirect the output from t_debug() and related calls such as t_write_file(). for example, from a server-side test you would probably need to redirect it to STDERR:
sub handler {
plan $r, tests => 1;
local $Apache::TestUtil::DEBUG_OUTPUT = *STDERR;
t_write_file(/tmp/foo, bar);
...
}
left to its own devices, t_debug() will collide with the standard HTTP protocol during server-side tests, resulting in a situation both confusing difficult to debug. but STDOUT is left as the default, since you probably dont want debug output under normal circumstances unless running under verbose mode.
This function is exported by default.
t_write_file()
t_write_file($filename, @lines);
t_write_file() creates a new file at $filename or overwrites the existing file with the content passed in @lines. If only the $filename is passed, an empty file will be created.
If parent directories of $filename dont exist they will be automagically created.
The generated file will be automatically deleted at the end of the programs execution.
This function is exported by default.
t_append_file()
t_append_file($filename, @lines);
t_append_file() is similar to t_write_file(), but it doesnt clobber existing files and appends @lines to the end of the file. If the file doesnt exist it will create it.
If parent directories of $filename dont exist they will be automagically created.
The generated file will be registered to be automatically deleted at the end of the programs execution, only if the file was created by t_append_file().
This function is exported by default.
t_write_shell_script()
Apache::TestUtil::t_write_shell_script($filename, @lines);
Similar to t_write_file() but creates a portable shell/batch script. The created filename is constructed from $filename and an appropriate extension automatically selected according to the platform the code is running under.
It returns the extension of the created file.
t_write_perl_script()
Apache::TestUtil::t_write_perl_script($filename, @lines);
Similar to t_write_file() but creates a executable Perl script with correctly set shebang line.
t_open_file()
my $fh = t_open_file($filename);
t_open_file() opens a file $filename for writing and returns the file handle to the opened file.
If parent directories of $filename dont exist they will be automagically created.
The generated file will be automatically deleted at the end of the programs execution.
This function is exported by default.
t_mkdir()
t_mkdir($dirname);
t_mkdir() creates a directory $dirname. The operation will fail if the parent directory doesnt exist.
If parent directories of $dirname dont exist they will be automagically created.
The generated directory will be automatically deleted at the end of the programs execution.
This function is exported by default.
t_rmtree()
t_rmtree(@dirs);
t_rmtree() deletes the whole directories trees passed in @dirs.
This function is exported by default.
t_chown()
Apache::TestUtil::t_chown($file);
Change ownership of $file to the tests User/Group. This function is noop on platforms where chown(2) is unsupported (e.g. Win32).
t_is_equal()
t_is_equal($a, $b);
t_is_equal() compares any two datastructures and returns 1 if they are exactly the same, otherwise 0. The datastructures can be nested hashes, arrays, scalars, undefs or a combination of any of these. See t_cmp() for an example.
If $b is a regex reference, the regex comparison $a =~ $b is performed. For example:
t_is_equal($server_version, qr{^Apache});
If comparing non-scalars make sure to pass the references to the datastructures.
This function is exported by default.
t_server_log_error_is_expected()
If the handlers execution results in an error or a warning logged to the error_log file which is expected, its a good idea to have a disclaimer printed before the error itself, so one can tell real problems with tests from expected errors. For example when testing how the package behaves under error conditions the error_log file might be loaded with errors, most of which are expected.
For example if a handler is about to generate a run-time error, this function can be used as:
use Apache::TestUtil;
...
sub handler {
my $r = shift;
...
t_server_log_error_is_expected();
die "failed because ...";
}
After running this handler the error_log file will include:
*** The following error entry is expected and harmless ***
[Tue Apr 01 14:00:21 2003] [error] failed because ...
When more than one entry is expected, an optional numerical argument, indicating how many entries to expect, can be passed. For example:
t_server_log_error_is_expected(2);
will generate:
*** The following 2 error entries are expected and harmless ***
If the error is generated at compile time, the logging must be done in the BEGIN block at the very beginning of the file:
BEGIN {
use Apache::TestUtil;
t_server_log_error_is_expected();
}
use DOES_NOT_exist;
After attempting to run this handler the error_log file will include:
*** The following error entry is expected and harmless ***
[Tue Apr 01 14:04:49 2003] [error] Cant locate "DOES_NOT_exist.pm"
in @INC (@INC contains: ...
Also see t_server_log_warn_is_expected() which is similar but used for warnings.
This function is exported by default.
t_server_log_warn_is_expected()
t_server_log_warn_is_expected() generates a disclaimer for expected warnings.
See the explanation for t_server_log_error_is_expected() for more details.
This function is exported by default.
t_client_log_error_is_expected()
t_client_log_error_is_expected() generates a disclaimer for expected errors. But in contrast to t_server_log_error_is_expected() called by the client side of the script.
See the explanation for t_server_log_error_is_expected() for more details.
For example the following client script fails to find the handler:
use Apache::Test;
use Apache::TestUtil;
use Apache::TestRequest qw(GET);
plan tests => 1;
t_client_log_error_is_expected();
my $url = "/error_document/cannot_be_found";
my $res = GET($url);
ok t_cmp(404, $res->code, "test 404");
After running this test the error_log file will include an entry similar to the following snippet:
*** The following error entry is expected and harmless ***
[Tue Apr 01 14:02:55 2003] [error] [client 127.0.0.1]
File does not exist: /tmp/test/t/htdocs/error
When more than one entry is expected, an optional numerical argument, indicating how many entries to expect, can be passed. For example:
t_client_log_error_is_expected(2);
will generate:
*** The following 2 error entries are expected and harmless ***
This function is exported by default.
t_client_log_warn_is_expected()
t_client_log_warn_is_expected() generates a disclaimer for expected warnings on the client side.
See the explanation for t_client_log_error_is_expected() for more details.
This function is exported by default.
t_catfile(a, b, c)
This function is essentially File::Spec->catfile, but on Win32 will use Win32::GetLongpathName() to convert the result to a long path name (if the result is an absolute file). The function is not exported by default.
t_catfile_apache(a, b, c)
This function is essentially File::Spec::Unix->catfile, but on Win32 will use Win32::GetLongpathName() to convert the result to a long path name (if the result is an absolute file). It is useful when comparing something to that returned by Apache, which uses a Unix-style specification with forward slashes for directory separators. The function is not exported by default.
t_start_error_log_watch(), t_finish_error_log_watch()
This pair of functions provides an easy interface for checking the presence or absense of any particular message or messages in the httpd error_log that were generated by the httpd daemon as part of a test suite. It is likely, that you should proceed this with a call to one of the t_*_is_expected() functions.
t_start_error_log_watch();
do_it;
ok grep {...} t_finish_error_log_watch()
Download (0.15MB)
Added: 2007-07-30 License: Perl Artistic License Price:
816 downloads
braa 0.8
Braa is a tool for making SNMP queries. more>>
Braa is a tool for making SNMP queries. It is a software able to query hundreds or thousands of hosts simultaneously, while being completely single-threaded.
The intended usage of such a tool is of course making SNMP queries - but unlike snmpget or snmpwalk from net-snmp, it is able to query dozens or hundreds of hosts simultaneously, and in a single process. Thus, it consumes very few system resources and does the scanning VERY fast.
Braa implements its OWN snmp stack, so it does NOT need any SNMP libraries like net-snmp. The implementation is very dirty, supports only several data types, and in any case cannot be stated standard-conforming! It was designed to be fast, and it is fast. For this reason (well, and also because of my laziness ;), there is no ASN.1 parser in braa - you HAVE to know the numerical values of OIDs (for instance .1.3.6.1.2.1.1.5.0 instead of system.sysName.0
<<lessThe intended usage of such a tool is of course making SNMP queries - but unlike snmpget or snmpwalk from net-snmp, it is able to query dozens or hundreds of hosts simultaneously, and in a single process. Thus, it consumes very few system resources and does the scanning VERY fast.
Braa implements its OWN snmp stack, so it does NOT need any SNMP libraries like net-snmp. The implementation is very dirty, supports only several data types, and in any case cannot be stated standard-conforming! It was designed to be fast, and it is fast. For this reason (well, and also because of my laziness ;), there is no ASN.1 parser in braa - you HAVE to know the numerical values of OIDs (for instance .1.3.6.1.2.1.1.5.0 instead of system.sysName.0
Download (0.039MB)
Added: 2006-07-06 License: GPL (GNU General Public License) Price:
1208 downloads
Statistics::Cluto 0.01
Statistics::Cluto package contains Perl binding for CLUTO. more>>
Statistics::Cluto package contains Perl binding for CLUTO.
SYNOPSIS
use Statistics::Cluto;
use Data::Dumper;
my $c = new Statistics::Cluto;
$c->set_dense_matrix(4, 5, [
[8, 8, 0, 3, 2],
[2, 9, 9, 1, 4],
[7, 6, 1, 2, 3],
[1, 7, 8, 2, 1]
]);
$c->set_options({
rowlabels => [ row0, row1, row2, row3 ],
collabels => [ col0, col1, col2, col3, col4 ],
nclusters => 2,
rowmodel => CLUTO_ROWMODEL_NONE,
colmodel => CLUTO_COLMODEL_NONE,
pretty_format => 1,
});
my $clusters = $c->VP_ClusterRB;
print Dumper $clusters;
my $cluster_features = $c->V_GetClusterFeatures;
print Dumper $cluster_features;
<<lessSYNOPSIS
use Statistics::Cluto;
use Data::Dumper;
my $c = new Statistics::Cluto;
$c->set_dense_matrix(4, 5, [
[8, 8, 0, 3, 2],
[2, 9, 9, 1, 4],
[7, 6, 1, 2, 3],
[1, 7, 8, 2, 1]
]);
$c->set_options({
rowlabels => [ row0, row1, row2, row3 ],
collabels => [ col0, col1, col2, col3, col4 ],
nclusters => 2,
rowmodel => CLUTO_ROWMODEL_NONE,
colmodel => CLUTO_COLMODEL_NONE,
pretty_format => 1,
});
my $clusters = $c->VP_ClusterRB;
print Dumper $clusters;
my $cluster_features = $c->V_GetClusterFeatures;
print Dumper $cluster_features;
Download (0.027MB)
Added: 2007-05-22 License: Perl Artistic License Price:
885 downloads
Bandwidth Monitor NG 0.6
Bandwidth Monitor NG is a small and simple console-based live bandwidth monitor. more>>
Bandwidth Monitor NG is a small and simple console-based live bandwidth monitor.
I have sucessfully tested on (if you have any other sucessfull or unsucessfull, please mail me):
Linux 2.4, Linux 2.6
FreeBSD 4.8, 5.3
MacOS X 10.1, 10.2, 10.3
Solaris 10 64bit x86
SunOS 5.9 sparc Solaris 9
OpenBSD 3.4, 3.6
NetBSD 1.6.1, 2.0
IRIX64 6.5
Main features:
- supports /proc/net/dev, netstat, getifaddr, sysctl, kstat and libstatgrab
- unlimited number of interfaces supported
- interfaces are added or removed dynamically from list
- white-/blacklist of interfaces
- output of KB/s, Kb/s, packets, errors, average, max and total sum
- output in curses, plain console, CSV or HTML
- configfile
Enhancements:
- Changes in this release include curses2 output (a nice bar chart), disk input for BSD, Mac OS X, Linux, and Solaris, Win32 network bandwidth support, use of autotools, and lots of fixes.
<<lessI have sucessfully tested on (if you have any other sucessfull or unsucessfull, please mail me):
Linux 2.4, Linux 2.6
FreeBSD 4.8, 5.3
MacOS X 10.1, 10.2, 10.3
Solaris 10 64bit x86
SunOS 5.9 sparc Solaris 9
OpenBSD 3.4, 3.6
NetBSD 1.6.1, 2.0
IRIX64 6.5
Main features:
- supports /proc/net/dev, netstat, getifaddr, sysctl, kstat and libstatgrab
- unlimited number of interfaces supported
- interfaces are added or removed dynamically from list
- white-/blacklist of interfaces
- output of KB/s, Kb/s, packets, errors, average, max and total sum
- output in curses, plain console, CSV or HTML
- configfile
Enhancements:
- Changes in this release include curses2 output (a nice bar chart), disk input for BSD, Mac OS X, Linux, and Solaris, Win32 network bandwidth support, use of autotools, and lots of fixes.
Download (0.066MB)
Added: 2007-03-01 License: GPL (GNU General Public License) Price:
971 downloads
ChainBuilder ESB for Linux 2.0
ChainBuilder ESB is an open source solution for use in Service Oriented Architecture (SOA) environments. ChainBuilder ESB creates standards-based components though drag and drop graphical user interfa more>>
ChainBuilder ESB is an open source Enterprise Service Bus. ChainBuilder ESB allows IT developers with Service Oriented Architecture (SOA) infrastructures to create standards-based ESB components through Eclipse-based graphical user interfaces. Most organizations SOAs need to include strategic backend systems that operate with non-XML data formats and non-WebServices communication protocols. Bostech focus on usability ensured the initial offerings of ChainBuilder ESB had industry standard editors to manage EDI X12, HL7, fixed and variable formats and communication components for TCP/IP, FTP and file protocols and database components for JMS and ETL integrations - the formats and protocols that organizations with mature applications absolutely require. ChainBuilder ESB also has uncommon high-end open source features, like an AJAX-based Console web interface for monitoring and controlling the production environment, usually found only with expensive proprietary systems. Bostech Corporation is deploys a dual-license distribution model for ChainBuilder ESB. Developers can download the open source software for Windows, Linux and Unix under the common GPL license at http://www.chainforge.net. A commercial license and subscription support is also available for enterprises and software vendors.
System Requirements: P4/1GB ram/10GB HD min; dual 3.0Ghz/2GB ram preferred
System Requirements: 2.0, Oct 2008 1.3.1, July 2008, incls Java 6 1.2, Mar 2008, incls ETL and Vista 1.1, Aug 2007, incls HL7, POP3, SMTP and framework; 1.0, Jan 2007, incls console and JDBC support; Beta Release, Dec 2006, incls source code and Linux support; Alpha Release, Sep 2006, incls Windows support;
<<less Download (365.00MB)
Added: 2009-04-02 License: Freeware Price: $0
204 downloads
Secleted [ 0 ] software to compare
- Page: 1 of 1
- 1
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above 6.1.2 search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed
