Sponsored Content
Full Discussion: Unix Shell Scripting
Top Forums UNIX for Dummies Questions & Answers Unix Shell Scripting Post 302686489 by Don Cragun on Tuesday 14th of August 2012 04:57:21 PM
Old 08-14-2012
First, there are two flavors of the echo utility. The BSD-based version of echo concatenates all of the operands it is given and write them to standard output followed by a <newline>. If the -n option is present it doesn't output the <newline>. I assume this is the version of echo you have on your system. (On the UNIX System V-based version of echo -n is not an option; it is just another operand to be printed. But there are several escape sequences in the string operands that the System V echo will translate ("\t" -> <tab>, "\n" -> <newline>, "\0" -> skip the remainder of this and any following operand and skip the normal trailing <newline>, etc.) that the BSD echo will not change.) If you want to output some text without the normal trailing <newline> in a way that will be portable to all UNIX and Linux systems, use the printf utility instead of echo.

So, your cout << "string" being roughly equivalent to [icode]echo -n "string" is pretty close. But echo $1 is also an output statement; not an input statement. I'm more of a C guy, than C++. In C it is roughly equivalent to printf("%s\n", argv[1]);. The equivalence is would be exact if you used "$1" instead of $1 because if the string isn't quoted and you have the default setting for $IFS, any sequences of one or more <space> and <tab> characters will be translated to a single space and passed to the echo command as individual operands instead of as a single string.

In the shells (bash, ksh, sh, ...), $n (1 <= n <= 9) refers to the 9th argument given to to the shell script when it was invoked. If you use ${n}, n can be greater than 9. $0 refers to the name of the script (like argv[0] in a C or C++ program). So, if you have a regular file with the execute bit set named "script" that contains something like:
Code:
#!/bin/ksh
echo -n "There once was a "
echo $1
echo -n "that "
echo $2
echo -n "who liked to " 
echo $3
echo -n "There once was a " $1 " that " $2 " who liked to " $3

and invoked it as:
Code:
script man "spent a lot of time in a swimming pool" "win gold medals!"

the output should be something like:
Code:
There once was a man
 that spent a lot of time in a swimming pool
 who liked to win gold medals!
There once was a man that spent a lot of time in a swimming pool who liked to win gold medals!

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix shell scripting

I need to write a script which analyses an invoice file, counting the amount of pages in the file to be printed per account number and per invoice. The account numbers are stored in another file which has instructions on what do with ach customers invoice as per their account number. please... (6 Replies)
Discussion started by: la_burton
6 Replies

2. Shell Programming and Scripting

difference between AIX shell scripting and Unix shell scripting.

please give the difference between AIX shell scripting and Unix shell scripting. (2 Replies)
Discussion started by: haroonec
2 Replies

3. Shell Programming and Scripting

Unix shell scripting

Hi, we are writing this fields dynamically retrieved from database and writing into the file. $bmpRec = $bmpRec.'|'.$cust_id; # sp4 $bmpRec = $bmpRec.'|'.$serv_id; # sp5 $bmpRec = $bmpRec.'|'.$site_id; # sp6 $bmpRec = $bmpRec.'|'.$loc_id; # sp7 ... (4 Replies)
Discussion started by: Maruthi Kunnuru
4 Replies

4. Shell Programming and Scripting

Unix Shell Scripting

Hi All, Greetings!! I am trying to write a script that will get me the syslog.log file output of last week... That is ...my cron will run on Monday and will get me the syslog output of previous week , last monday-last sunday. I tried using date formatting and tail..but did not succeed.... (4 Replies)
Discussion started by: premamadhuri
4 Replies

5. UNIX for Advanced & Expert Users

Need your Help on Unix Shell Scripting.........

Hi Friends, 1. Bash Shell Scrpt to take backup at evening 2. I need a bash shell script for killing all processes. (5 Replies)
Discussion started by: vinayraj
5 Replies

6. Shell Programming and Scripting

Unix Shell Scripting

I 'm new to unix shell scripting can some one guide me to any e-book or link from where i can learn unix shell scripting .. i want to learn create interactive scripts for my day to day solaris work. Any help would be appreciated (1 Reply)
Discussion started by: fugitive
1 Replies

7. UNIX for Dummies Questions & Answers

Unix Shell Scripting( Calling from Unix to PLSQL)

Hello Experts, I have the following questions to be discussed here at this esteemed discussion forum. I have two Excel sheets which contain Unix Commands llike creating directory the structure/ftp/Copy/Zip etc to basically create an environment. I need help in understanding some of... (1 Reply)
Discussion started by: faizsaadq
1 Replies

8. Shell Programming and Scripting

UNIX shell scripting

I am new to Unix.. Can someone please help me to understand the concept of Login shell and non login shell ? what exactly the difference between them :confused: (1 Reply)
Discussion started by: lokita jain
1 Replies

9. Programming

unix Shell scripting

Hi All, need help to complete the automation but stuck at a perticular situation below is the code <code> fixed_function_name { code.... code.... variable_map= { a="/a" b="/b" c="/c" so on... } (7 Replies)
Discussion started by: yadavricky
7 Replies

10. UNIX for Beginners Questions & Answers

UNIX Shell Scripting

Describe in short the word completion feature of the tcsh Completion works anywhere in the command line, not at just the end, for both commands and filenames. Type part of a word and hit the Tab key, and the shell replaces the incomplete word with the complete one in the input buffer. The... (1 Reply)
Discussion started by: Elena Lauren
1 Replies
ECHO(1P)						     POSIX Programmer's Manual							  ECHO(1P)

PROLOG
This manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (consult the correspond- ing Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux. NAME
echo - write arguments to standard output SYNOPSIS
echo [string ...] DESCRIPTION
The echo utility writes its arguments to standard output, followed by a <newline>. If there are no arguments, only the <newline> is writ- ten. OPTIONS
The echo utility shall not recognize the "--" argument in the manner specified by Guideline 10 of the Base Definitions volume of IEEE Std 1003.1-2001, Section 12.2, Utility Syntax Guidelines; "--" shall be recognized as a string operand. Implementations shall not support any options. OPERANDS
The following operands shall be supported: string A string to be written to standard output. If the first operand is -n, or if any of the operands contain a backslash ( '' ) charac- ter, the results are implementation-defined. On XSI-conformant systems, if the first operand is -n, it shall be treated as a string, not an option. The following character sequences shall be recognized on XSI-conformant systems within any of the arguments: a Write an <alert>.  Write a <backspace>. c Suppress the <newline> that otherwise follows the final argument in the output. All characters following the 'c' in the arguments shall be ignored. f Write a <form-feed>. Write a <newline>. Write a <carriage-return>. Write a <tab>. v Write a <vertical-tab>. \ Write a backslash character. num Write an 8-bit value that is the zero, one, two, or three-digit octal number num. STDIN
Not used. INPUT FILES
None. ENVIRONMENT VARIABLES
The following environment variables shall affect the execution of echo: LANG Provide a default value for the internationalization variables that are unset or null. (See the Base Definitions volume of IEEE Std 1003.1-2001, Section 8.2, Internationalization Variables for the precedence of internationalization variables used to determine the values of locale categories.) LC_ALL If set to a non-empty string value, override the values of all the other internationalization variables. LC_CTYPE Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments). LC_MESSAGES Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error. NLSPATH Determine the location of message catalogs for the processing of LC_MESSAGES . ASYNCHRONOUS EVENTS
Default. STDOUT
The echo utility arguments shall be separated by single <space>s and a <newline> shall follow the last argument. Output transformations shall occur based on the escape sequences in the input. See the OPERANDS section. STDERR
The standard error shall be used only for diagnostic messages. OUTPUT FILES
None. EXTENDED DESCRIPTION
None. EXIT STATUS
The following exit values shall be returned: 0 Successful completion. >0 An error occurred. CONSEQUENCES OF ERRORS
Default. The following sections are informative. APPLICATION USAGE
It is not possible to use echo portably across all POSIX systems unless both -n (as the first argument) and escape sequences are omitted. The printf utility can be used portably to emulate any of the traditional behaviors of the echo utility as follows (assuming that IFS has its standard value or is unset): * The historic System V echo and the requirements on XSI implementations in this volume of IEEE Std 1003.1-2001 are equivalent to: printf "%b " "$*" * The BSD echo is equivalent to: if [ "X$1" = "X-n" ] then shift printf "%s" "$*" else printf "%s " "$*" fi New applications are encouraged to use printf instead of echo. EXAMPLES
None. RATIONALE
The echo utility has not been made obsolescent because of its extremely widespread use in historical applications. Conforming applications that wish to do prompting without <newline>s or that could possibly be expecting to echo a -n, should use the printf utility derived from the Ninth Edition system. As specified, echo writes its arguments in the simplest of ways. The two different historical versions of echo vary in fatally incompati- ble ways. The BSD echo checks the first argument for the string -n which causes it to suppress the <newline> that would otherwise follow the final argument in the output. The System V echo does not support any options, but allows escape sequences within its operands, as described for XSI implementations in the OPERANDS section. The echo utility does not support Utility Syntax Guideline 10 because historical applications depend on echo to echo all of its arguments, except for the -n option in the BSD version. FUTURE DIRECTIONS
None. SEE ALSO
printf COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2003 Edition, Standard for Information Technol- ogy -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html . IEEE
/The Open Group 2003 ECHO(1P)
All times are GMT -4. The time now is 12:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy