The last example on page Functions suggests that bash cannot do this.
The shell ksh has a namespace facility. So if you wrote your code as in file user6:
then produces:
For a system like:
And, apparently if you needed to use the namespace function outside of the namespace, you could use it as .mine._test.
I have not used the namepace idea before, but it seems to work. See man ksh for some details.
Is it possible to make function variables local?
I mean for example, I have a script variable 'name' and in function I have declared variable 'name'
I need to have script's 'name' have the same value as it was before calling the function with the same declaration.
The way to preserve a... (5 Replies)
Hi All,
Can you please tell me how to execute local function written in a shell script with awk.
i tried with system command but its giving an error. (1 Reply)
Hi,
I have the following statement which parses a string for me and prints it out:
l_comp="dc000.runksh.test.ksh|
$g_sql/dc0000.runksh_test.sql|new.dat|control.ctl"
echo $l_comp | awk -F"|" '{ for ( i = 1; i <= NF; i++) { print $i; } } '
Rather then printing the data, I would like to... (5 Replies)
The following code doesn't work properly which means it doesn't displays remote output.
#!/bin/ksh
#################### Function macAddressFinder ########################
macAddressFinder()
{
`ifconfig -a > ipInterfaces`
`cat ipInterfaces`
}... (2 Replies)
I wrote the following Makefile:
dirs := a b c d
files := $(foreach dir,$(dirs),$(wildcard $(dir)/*))
.PHONY: all
all:
touch $(files)
The first two lines are taken from GNU make tutorial, Section 8.5 The foreach Function. I would expect the recipe
touch $(files)
to be... (2 Replies)
As I know threads share the memory. But, what about the local variables in the thread function? if i call multiple threads would they allocate seperate local variables for themselves?
like
thread_func()
{
int i, j;
string...
}
Are the above local variables defined for each of... (1 Reply)
Hi,
If I have a code like this, what are the potential problems do you see?
const char* const retString() {
return "hello"; /* string literal */
}
My questions are:
a) Since the string literal which is already a constant read only data (cannot be... (4 Replies)
Legends,
I am not able to set "expr" function in ksh script.
Below is the sample code i used, and output is as "Syntax error"
Please help me to come out of it.
OUTPUT (9 Replies)
Hi,
I am working in UEFI EDK2 Bios source. We created a platform related new package in the EDK2 source. I find a strange issue with the platform related code we added.
When I did source level debugging I noticed the
local variable in a C function is not getting created in stack when its... (6 Replies)
Hi All,
Good Day, seeking for your assistance on how to not perform my 2nd, 3rd,4th etc.. function if my 1st function is in else condition.
#Body
function1()
{
if
then
echo "exist"
else
echo "not exist"
}
#if not exist in function1 my all other function will not proceed.... (4 Replies)
Discussion started by: meister29
4 Replies
LEARN ABOUT DEBIAN
go-test
GO-TEST(1) General Commands Manual GO-TEST(1)NAME
go - tool for managing Go source code
SYNOPSIS
go test [-c] [-i] [ build flags ] [ packages ] [ flags for test binary ]
DESCRIPTION
"Go test" automates testing the packages named by the import paths. It prints a summary of the test results in the format:
ok archive/tar 0.011s
FAIL archive/zip 0.022s
ok compress/gzip 0.033s
...
followed by detailed output for each failed package.
"Go test" recompiles each package along with any files with names matching the file pattern "*_test.go". These additional files can con-
tain test functions, benchmark functions, and example functions. See go-testfunc(7) for more.
By default, go test needs no arguments. It compiles and tests the package with source in the current directory, including tests, and runs
the tests.
The package is built in a temporary directory so it does not interfere with the non-test installation.
OPTIONS
In addition to the build flags, the flags handled by 'go test' itself are:
-c Compile the test binary to pkg.test but do not run it.
-i Install packages that are dependencies of the test. Do not run the test.
The test binary also accepts flags that control execution of the test; these flags are also accessible by 'go test'. See go-testflag(7)
for details.
For more about build flags, see go-build(1).
For more about specifying packages, see go-packages(7).
SEE ALSO go-build(1), go-vet(1).
AUTHOR
This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others).
2012-05-13 GO-TEST(1)