03-04-2010
You could display the wanted values by testing if no arguments are given (would have to test the one given is valid anyway...)
10 More Discussions You Might Find Interesting
1. Programming
Hi to all...
I'm currently running a C++ program in Unix environment and it is dependent to a Unix environment variable with a date value.
ex: echo $DateToday
20060403
I want to change that date in my C++ program, changing the value date to 20061120 and revert back to original... (6 Replies)
Discussion started by: d3ck_tm
6 Replies
2. Programming
I have function declaration in Java and same function definition written in C programming language.. A JNI call from Java is made to a fuction...Function would set the environment variable { putenv(cEnvString1);} using C-built -in function ..and later return the encrypted string...
putenv is... (6 Replies)
Discussion started by: shafi2all
6 Replies
3. UNIX for Dummies Questions & Answers
Dear all,
I have a data sample...
Dose: Summed
ROI: Bladder
**************************
Bin Dose Volume
001 0.700 100.000
002 0.715 99.998
168 3.142 0.368
169 3.157 0.338
170 3.171 0.292
Dose: Summed
ROI:... (2 Replies)
Discussion started by: tintin72
2 Replies
4. Programming
Hi,
I already have one CPP program which invokes the C program.And the C program contains whole function definitions..!This is a working program..I have to enable the logs in both CPP as well as in the C program ..!So I am reading the enviornmental variable log path from the CPP and doing the... (2 Replies)
Discussion started by: Kattoor
2 Replies
5. Shell Programming and Scripting
Hi All,
I'm trying to write an menu driven program to automate some functions which involve loging to multiple hosts. The hosts can differ for every use, so I thought I would use an config file to get the hostnames. Now I need to set those values in the config file to environment variable to... (6 Replies)
Discussion started by: arun_maffy
6 Replies
6. Shell Programming and Scripting
Hi all,
I am fairly new to unix scripting and will like to know how to dynamically set the name of an environment variable to be used.
We have a .env file where we defined the names and locations of data files, trigger files, directories .... etc
Example of variables defined in .env... (4 Replies)
Discussion started by: Morelia
4 Replies
7. Shell Programming and Scripting
shell script: #!/bin/csh set VAR=12345 echo $VAR
will peacefully give the output 12345 at shell. I need to use C++ to do the same in some part of the code:
string str = "12345";
retValue="set var1= "+str;
system(retValue1.c_str());
system("echo $var1");
This doesn't create a system... (1 Reply)
Discussion started by: harshvardhan360
1 Replies
8. UNIX for Dummies Questions & Answers
I want to set a enviroment variable
VDC_DIR to a particular directory.
I am doing it as
export VDC_DIR=/abc
it gets set but when i logout and do relogin than its not there.
one way could be setting it in .profile file.
but i have seen it on another box where it is not present in... (2 Replies)
Discussion started by: Jcpratap
2 Replies
9. UNIX for Dummies Questions & Answers
I am trying to install timbl- memory based learner tools in ubuntu. it after unpacking the tar file it brings the following msg
No package 'ticcutils' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you... (1 Reply)
Discussion started by: gbdaw
1 Replies
10. UNIX for Dummies Questions & Answers
I am wondering about the following:
stty columns 140
I have found that a number of times I need to set my display columns to a high number (such as 140) but I have to do this every time I login to use putty/ssh. Can we set this with an environmental variable so that it is permanent?
Also... (4 Replies)
Discussion started by: newbie2010
4 Replies
LEARN ABOUT DEBIAN
test::unit::procedural
Test::Unit::Procedural(3pm) User Contributed Perl Documentation Test::Unit::Procedural(3pm)
NAME
Test::Unit::Procedural - Procedural style unit testing interface
SYNOPSIS
use Test::Unit::Procedural;
# your code to be tested goes here
sub foo { return 23 };
sub bar { return 42 };
# define tests
sub test_foo { assert(foo() == 23, "Your message here"); }
sub test_bar { assert(bar() == 42, "I will be printed if this fails"); }
# set_up and tear_down are used to
# prepare and release resources need for testing
sub set_up { print "hello world
"; }
sub tear_down { print "leaving world again
"; }
# run your test
create_suite();
run_suite();
DESCRIPTION
Test::Unit::Procedural is the procedural style interface to a sophisticated unit testing framework for Perl that is derived from the JUnit
testing framework for Java by Kent Beck and Erich Gamma. While this framework is originally intended to support unit testing in an object-
oriented development paradigm (with support for inheritance of tests etc.), Test::Unit::Procedural is intended to provide a simpler inter-
face to the framework that is more suitable for use in a scripting style environment. Therefore, Test::Unit::Procedural does not provide
much support for an object-oriented approach to unit testing - if you want that, please have a look at Test::Unit::TestCase.
You test a given unit (a script, a module, whatever) by using Test::Unit::Procedural, which exports the following routines into your names-
pace:
assert()
used to assert that a boolean condition is true
create_suite()
used to create a test suite consisting of all methods with a name prefix of "test"
run_suite()
runs the test suite (text output)
add_suite()
used to add test suites to each other
For convenience, "create_suite()" will automatically build a test suite for a given package. This will build a test case for each subrou-
tine in the package given that has a name starting with "test" and pack them all together into one TestSuite object for easy testing. If
you dont give a package name to "create_suite()", the current package is taken as default.
Test output is one status line (a "." for every successful test run, or an "F" for any failed test run, to indicate progress), one result
line ("OK" or "!!!FAILURES!!!"), and possibly many lines reporting detailed error messages for any failed tests.
Please remember, Test::Unit::Procedural is intended to be a simple and convenient interface. If you need more functionality, take the
object-oriented approach outlined in Test::Unit::TestCase.
AUTHOR
Copyright (c) 2000-2002, 2005 the PerlUnit Development Team (see Test::Unit or the AUTHORS file included in this distribution).
All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
SEE ALSO
o Test::Unit::TestCase
o the procedural style examples in the examples directory
perl v5.8.8 2006-09-13 Test::Unit::Procedural(3pm)