This line is correct syntax to start a function:
usage() {
This line (and many more like it) is not correct syntax to start a function.
function searchFile() {
This "if" test is misplaced, syntactically incorrect and upsetting the whole structure of the script.
Quote:
if [ $# != 2 ] then
usage() {
You probably meant to declare the function "usage" first, then later in the script ....
Code:
if [ $# -ne 2 ]
then
usage
fi
There are more typos in the script, some of which matter (like "Case" instead of "case") and some less important like the spelling of "successful"!
As others suggest, work you way through the script correcting each error. As this strikes me as an edit to a complex script perhaps introduce the changes bit-by-bit and test at every stage.
Quote:
LOG_NAME_DATE=`date +%y%m%d% -%H%M%S`
This does not produce what you think. Even after removing the space character there is an extra % character. Try it?
i am new to solaris
i have one module which contain certain header files and sub modules
i want ot execute the module and c what the values are beeing assigned to variables
is makefile only solution for this
is there any editor to help it,so that i can c the flow of the program and also... (1 Reply)
Hi,
In our program, we are using SIGTERM and i tired to put break point in this function. But my debuger is unable to brake at that point.
I am working on Mac X and using XCode.
Thanks (0 Replies)
Hi,
In our program, we are using SIGTERM and i tired to put break point in this function. But my debuger is unable to brake at that point.
I am working on Mac X and using XCode.
Thanks (1 Reply)
When I run a lengthy script in debug mode i need to capture all the steps which are executed.
e.g
ksh -x script.ksh
+ test -f /proc/mounts
+ /bin/ls -l /proc/21326/exe
+ is=ksh
+ test ksh = ksh
+ test -s /etc/ksh.kshrc
+ . /etc/ksh.kshrc
+ trap 1 2 3
+ who am i
+ awk {print $1}
+... (2 Replies)
Hi All,
I have a question on debugging the .so file.
When I am running makefile I am getting a .so file and we are using that .so file for executing our code.But I want to know
1.Can I use dbx or gdb to debug a .so file?
2.How can i generate .out file so that i can use that in dbx or gdb... (1 Reply)
Can you help please ?
./get_df.sh: syntax error at line 13 : `then' unexpected
#!/bin/ksh
while :
do
PER=`df -h /DATA/ | nawk '{if (NR != 1) { sub (/%/,""); print $(NF-1)}}'`
if
then
if]
then
mailx -s "FS over 90 per" me@company.com
touch... (2 Replies)
Hello, I was looking at kernel log's and found some parts what was "interesting"
I previously started looking what has been going on in my computer because I had hacker attacks on my machine.
Installed Avira & Little Snitch - softwares
Previously my computer opened few folders what I have... (1 Reply)
How can I debug this script?
I want to know what it is doing or not doing?
#!/bin/bash
#
#
if ; then
# Do the thing you want before suspend here
echo "we are suspending." > /tmp/systemd_suspend_test.txt
elif ; then
# Do the thing you want after resume here
echo "and we are... (21 Replies)
Discussion started by: drew77
21 Replies
LEARN ABOUT OSX
locale::script
Locale::Script(3pm) Perl Programmers Reference Guide Locale::Script(3pm)NAME
Locale::Script - standard codes for script identification
SYNOPSIS
use Locale::Script;
$script = code2script('phnx'); # 'Phoenician'
$code = script2code('Phoenician'); # 'Phnx'
$code = script2code('Phoenician',
LOCALE_CODE_NUMERIC); # 115
@codes = all_script_codes();
@scripts = all_script_names();
DESCRIPTION
The "Locale::Script" module provides access to standards codes used for identifying scripts, such as those defined in ISO 15924.
Most of the routines take an optional additional argument which specifies the code set to use. If not specified, the default ISO 15924
four-letter codes will be used.
SUPPORTED CODE SETS
There are several different code sets you can use for identifying scripts. A code set may be specified using either a name, or a constant
that is automatically exported by this module.
For example, the two are equivalent:
$script = code2script('phnx','alpha');
$script = code2script('phnx',LOCALE_SCRIPT_ALPHA);
The codesets currently supported are:
alpha, LOCALE_SCRIPT_ALPHA
This is a set of four-letter (capitalized) codes from ISO 15924 such as 'Phnx' for Phoenician. It also includes additions to this set
included in the IANA language registry.
The Zxxx, Zyyy, and Zzzz codes are not used.
This is the default code set.
num, LOCALE_SCRIPT_NUMERIC
This is a set of three-digit numeric codes from ISO 15924 such as 115 for Phoenician.
ROUTINES
code2script ( CODE [,CODESET] )
script2code ( NAME [,CODESET] )
script_code2code ( CODE ,CODESET ,CODESET2 )
all_script_codes ( [CODESET] )
all_script_names ( [CODESET] )
Locale::Script::rename_script ( CODE ,NEW_NAME [,CODESET] )
Locale::Script::add_script ( CODE ,NAME [,CODESET] )
Locale::Script::delete_script ( CODE [,CODESET] )
Locale::Script::add_script_alias ( NAME ,NEW_NAME )
Locale::Script::delete_script_alias ( NAME )
Locale::Script::rename_script_code ( CODE ,NEW_CODE [,CODESET] )
Locale::Script::add_script_code_alias ( CODE ,NEW_CODE [,CODESET] )
Locale::Script::delete_script_code_alias ( CODE [,CODESET] )
These routines are all documented in the Locale::Codes::API man page.
SEE ALSO
Locale::Codes
The Locale-Codes distribution.
Locale::Codes::API
The list of functions supported by this module.
http://www.unicode.org/iso15924/
Home page for ISO 15924.
http://www.iana.org/assignments/language-subtag-registry
The IANA language subtag registry.
AUTHOR
See Locale::Codes for full author history.
Currently maintained by Sullivan Beck (sbeck@cpan.org).
COPYRIGHT
Copyright (c) 1997-2001 Canon Research Centre Europe (CRE).
Copyright (c) 2001-2010 Neil Bowers
Copyright (c) 2010-2012 Sullivan Beck
This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.16.2 2012-10-11 Locale::Script(3pm)