|
|
Sponsored Content
UNIX Standards and Benchmarks
UNIX & LINUX Benchmarks (Version 3.11)
Linux Benchmarks
ga 970a ud3 bench
Post 302609433 by thirnick on Tuesday 20th of March 2012 12:12:34 AM
03-20-2012
|
|
2 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
Can anybody provide me Pointers to Practice tests or any Material to prepare for Brainbench certification in Unix Shell Scripting? Also how good is this Certification for UNIX programmers. Is it worth it? I'm planning to take this certification in 2 weeks. Kindly let me know all the pros... (0 Replies)
Discussion started by: pavan_emani
0 Replies
2. Shell Programming and Scripting
Hi,
I have 2 sub routines for example.
use Benchmark 'cmpthese';
sub explicit {
print "\n print and calculate\n";
}
sub new_per_loop {
for (0..4){
print "\n print the loop \n";
}
}
cmpthese (10_000, {
'Explicit' => &explicit,
... (2 Replies)
Discussion started by: vanitham
2 Replies
LEARN ABOUT MOJAVE
test::use::ok5.18
Test::use::ok(3) User Contributed Perl Documentation Test::use::ok(3) NAME
Test::use::ok - Alternative to Test::More::use_ok SYNOPSIS
use ok 'Some::Module'; DESCRIPTION
According to the Test::More documentation, it is recommended to run "use_ok()" inside a "BEGIN" block, so functions are exported at compile-time and prototypes are properly honored. That is, instead of writing this: use_ok( 'Some::Module' ); use_ok( 'Other::Module' ); One should write this: BEGIN { use_ok( 'Some::Module' ); } BEGIN { use_ok( 'Other::Module' ); } However, people often either forget to add "BEGIN", or mistakenly group "use_ok" with other tests in a single "BEGIN" block, which can create subtle differences in execution order. With this module, simply change all "use_ok" in test scripts to "use ok", and they will be executed at "BEGIN" time. The explicit space after "use" makes it clear that this is a single compile-time action. SEE ALSO
Test::More CC0 1.0 Universal To the extent possible under law, XX has waived all copyright and related or neighboring rights to Test-use-ok. This work is published from Taiwan. <http://creativecommons.org/publicdomain/zero/1.0> POD ERRORS
Hey! The above document had some coding errors, which are explained below: Around line 45: Non-ASCII character seen before =encoding in 'XX'. Assuming UTF-8 perl v5.18.2 2012-09-11 Test::use::ok(3)