Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: awk doesn't understand 'read' statement!!!
Top Forums Shell Programming and Scripting awk doesn't understand 'read' statement!!! Post 302796857 by ravisingh on Sunday 21st of April 2013 02:54:11 AM
Old 04-21-2013
Don Cragun, that may be a good way to test our programs by giving standard input (without specifying any file name). I had run awk programs by giving stnd input.

Now, what I want to say is:
As many told that why I see a link between 'read' and 'continue/break', I also wondered why they wrote so. Because my 1st post reflects the connection. Based on the user input read by the read statement, either 'continue' is executed or 'break' is executed. See my codes, if user inputs 'y' , 'continue' is executed orelse 'break'. I hope this should show the connection.

Now , coming to the other point :--" what is the use of 'continue/break' if awk doesn't understand 'read' statement". You all are right to say that 'continue/break' is used in awk without user interference or without user input. The reason I told becz I have used programs which execute 'continue or break' based on the input as the example I gave you. so, I thought that if user input is not to be used, then the code doesn't need continue or break. If possible, may I expect anyone to give a small algorithm or example to show how without user input, 'continue/break' makes sense.

Alister thanks to say a way of reading stnd input. I will check how it works.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

my case statement doesn't work..

CO UNixware 7.1.1 Hi friends, I have chopped my case statementt out of my .profile and put it in another script called setsid. The case statement works when run from my .profile but not from my setsid file. All that the script does is set an environmental variable based on user input.... (7 Replies)
Discussion started by: sureshy
7 Replies

2. Shell Programming and Scripting

while read loop w/ a nested if statement - doesn't treat each entry individually

Hi - Trying to take a list of ldap suffixes in a file, run an ldapsearch command on them, then run a grep command to see if it's a match, if not, then flag that and send an email alert. The list file (ldaplist) would look like - *********** o=company a o=company b *********** **... (7 Replies)
Discussion started by: littlefrog
7 Replies

3. Shell Programming and Scripting

Not able to understand what's do the statement

Always, I have a confuse/not understand file descriptors. I know about the 0 for standard input 1 for standard output 2 for standard error and 3 to 9 is a additional file descriptor but it's a theoritical knowledge. Could you please give information about below two lines of code in AIX... (1 Reply)
Discussion started by: div_Neev
1 Replies

4. AIX

How to read or understand errors in errpt

Hello, after upgrading the memory to 96GB & 6 Dual Processor for P 550 ( and still not applied the parameters which some experienced posters said in post https://www.unix.com/aix/141835-oracle-database-running-slow-aix-nmon-topas-6.html ) I am getting system dumps. How to understand and... (1 Reply)
Discussion started by: filosophizer
1 Replies

5. Shell Programming and Scripting

My if statement doesn't work why?

I have the following and for some reason I can't have two options together. I mean if I choose -u and -p it won't work... why? #!/bin/bash resetTime=1 mytotalTime=0 totalHour=0 totalMin=0 averagemem=0 finalaverage=0 times=0 function usage() { cat << EOF USAGE: $0 file EOF } (10 Replies)
Discussion started by: bashily
10 Replies

6. UNIX for Dummies Questions & Answers

How to read and understand Sendmail 8.14 log files ?

Can some one please help me know how exactly to understand logs in sendmail 8.14.5. I am pretty new to sendmail. I am running rhel6 on my system and i installed sendmail on it. Its just a test enivornment and i am sending and receiving emails on my localshot only. Jun 13 18:32:38 serv1... (0 Replies)
Discussion started by: Rohit Bhanot
0 Replies

7. Red Hat

Grep doesn't understand escape sequence?

I ran the following grep and sed command. grep "\t" emp.txt sed -n '/\t/p' emp.txt grep treated the '\' as to escape t and took the pattern as literal t whereas sed took the pattern as tab. That means , grep doesn't understand escape sequence!!!!!! what to do to make grep... (8 Replies)
Discussion started by: ravisingh
8 Replies

8. Shell Programming and Scripting

How come this if statement doesn't work?

greetings, the following code isn't working as i expect it to. the first dbl brackets do but the second set gets ignored. ie: if i'm on t70c6n229 it echoes "Something" and i expect it not to. what am i missing? if " ]] || " ]]; then echo "Something" fi thanx! (9 Replies)
Discussion started by: crimso
9 Replies

9. Shell Programming and Scripting

Script doesn't understand if conditiojn with or

I Bourne shell I have a lines #!/bin/sh something for file in *_${Today}*.csv *_${Today}*.txt do if then echo "This file will be processed in separate script" continue fi something done The script doesn't understand if... (6 Replies)
Discussion started by: digioleg54
6 Replies

LEARN ABOUT V7

break

break(1)                                                           User Commands                                                          break(1)

NAME

       break, continue - shell built-in functions to escape from or advance within a controlling while, for, foreach, or until  loop

SYNOPSIS

   sh
       break [n]

       continue [n]

   csh
       break

       continue

   ksh
       *break [n]

       *continue [n]

DESCRIPTION

   sh
       The break utility exits from the enclosing for or while loop, if any. If n is specified, break n levels.

       The continue utility resumes the next iteration of the enclosing for or while loop. If n is specified, resume at the n-th enclosing loop.

   csh
       The  break  utility  resumes  execution after the end of the nearest enclosing foreach or while loop. The remaining commands on the current
       line are executed. This allows multilevel breaks to be written as a list of break commands, all on one line.

       The continue utility continues execution of the next iteration of the nearest enclosing while or foreach loop.

   ksh
       The break utility exits from the enclosed for, while, until, or select loop, if any. If n is specified,  then  break  n  levels.  If  n  is
       greater than the number of enclosing loops, the outermost enclosing loop shall be exited.

       The  continue utility resumes the next iteration of the enclosed for, while, until, or select loop. If n is specified then resume at the n-
       th enclosed loop. If n is greater than the number of enclosing loops, the outermost enclosing loop shall be used.

       On this man page, ksh(1) commands that are preceded by one or two * (asterisks) are treated specially in the following ways:

       1.  Variable assignment lists preceding the command remain in effect when the command completes.

       2.  I/O redirections are processed after variable assignments.

       3.  Errors cause a script that contains them to abort.

       4.  Words that follow a command preceded by ** that are in the format of a variable assignment are expanded with the same rules as a  vari-
           able  assignment.  This means that tilde substitution is performed after the = sign, and also that word splitting and file name genera-
           tion are not performed.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE         |      ATTRIBUTE VALUE        |
       +-----------------------------+-----------------------------+
       |Availability                 |SUNWcsu                      |
       +-----------------------------+-----------------------------+

SEE ALSO

       csh(1), exit(1), ksh(1), sh( 1), attributes(5)

SunOS 5.10                                                          17 Jul 2002                                                           break(1)
All times are GMT -4. The time now is 10:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy