Sponsored Content
Top Forums Shell Programming and Scripting Perl : How is file handling working here?? Post 302831881 by balajesuri on Friday 12th of July 2013 06:19:17 AM
Old 07-12-2013
Everytime you do read from a filehandle and store it in a scalar variable, then one line of input is read. (By one line, I mean the data until the next record separator).

Here is how it works internally:
When you open a filehandle, lets say, there's a mark that is at the beginning of file. The first time $rec = scalar <$INF> is encountered, the first line from file is read and referred by $rec. Now, the mark that we spoke of earlier, is at the character just after newline character (assuming newline as the default record separator). Now again when $rec = scalar <$INF> is encountered, one more line of data is read.

In the example code you provided in your post, a wrapper routine "readfile" reads one line of data and prints it.

The usual way of reading a file is to use a loop. Then again, that depends on what you really want to do:

Code:
open FH, "< /path/to/file";
while ($rec = <FH>) {
    print $rec;
}
close FH;

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

file handling problem in perl......

Hi, I am opening a file......then i am wrting some data into it......and i am reopening the file again but ......i get a error cannot open file....... $::file= "\adder\testfile.txt" open(TEST1,$::file); some write operation close(TEST1) open(TEST1,$::file) 'I GET A ERROR CAN OPEN... (2 Replies)
Discussion started by: vivekshankar
2 Replies

2. Shell Programming and Scripting

perl redirect output to file ..not working

here is simple perl script i wanted for my net connection ... just to check if default gateway is pingable or not if not write in log file but problem is that i can not write in file i can print on STDOUT but not in file ...why so ?? same thing was there when i was tying to write on sockets... (7 Replies)
Discussion started by: zedex
7 Replies

3. Shell Programming and Scripting

Perl revers File handling

Hi Experts, I have a big text file, so I want read it at eof to upper bound !. after I use a fseek to go SEEK_END, is it possible to step up upperbound? Best Regards. Note that I'm used perl script. (2 Replies)
Discussion started by: Zaxon
2 Replies

4. Programming

XML Handling in Perl

Hi there, I'm newby in perl and XML. I can read and parse Xml with XML-Node upper XML::Parser, but how can I create XML tags and pack my individual data in it then send through socket. PLZ lead me :) Thanks in Advance. (1 Reply)
Discussion started by: Zaxon
1 Replies

5. Shell Programming and Scripting

String handling is not working inside if loop

Hi All, I am comparing two strings inside an if condition if the strings are same then it should go inside the loop else it should execute code given in else part. But there is a but inside my script Even if the if condition is true it is not going inside the loop also it is executing... (4 Replies)
Discussion started by: usha rao
4 Replies

6. Shell Programming and Scripting

file handling in perl without using system command

Hi , Is there any way to achieve following using perl program (i.e without using system command). 1.system ("echo 'test' > /usr/spool/ship.csv"); 2.system ("cat /usr/ajay_test* >> /usr/spool/RAM/work/patil.csv"); 3.system("> /usr/spool/ajay.txt"); e.g for system("rm -f... (1 Reply)
Discussion started by: ajaypatil_am
1 Replies

7. Shell Programming and Scripting

Handling Parameters in Perl

Hi All, I'm pretty new to the forum and also to UNIX. I have a requirement for which I need some help. I have a script (example.script) where I get user inputs using the read command. I would need to pass the read-fetched input to a perl command (explained below) in my script. The part which... (3 Replies)
Discussion started by: bharath.gct
3 Replies

8. Programming

Perl help for file handling

$# some text $$ some text $@ some text $$. some text Mg1 some text Mg2 some text . . . Mg10 some text The above 10 lines are to be extracted except the lines starting from $#,$$.,... (4 Replies)
Discussion started by: baig.abdul
4 Replies

9. Shell Programming and Scripting

PERL error handling

I have a PERL command line embedded in a UNIX script. The script doesn't handle errors coming out of this command. I'm processing large files and occassionally I run out of disk space and end up with half a file. perl -p -e 's/\n/\r\n/g' < TR_TMP_$4 > $4 How do I handle errors coming out... (1 Reply)
Discussion started by: OTChancy
1 Replies

10. Shell Programming and Scripting

Perl file handling error

Hi, I am reading and file and writting each word to other file. where I have used array to store the data. I am getting below error as "Use of uninitialized value in concatenation (.) or string at customize_split_raw.pl line 51, <IN_FILE> " Where my line 51 code is 50 foreach... (8 Replies)
Discussion started by: Beginer123
8 Replies
FileHandle::Unget(3)					User Contributed Perl Documentation				      FileHandle::Unget(3)

NAME
FileHandle::Unget - FileHandle which supports multi-byte unget SYNOPSIS
use FileHandle::Unget; # open file handle my $fh = FileHandle::Unget->new("file") or die "cannot open filehandle: $!"; my $buffer; read($fh,$buffer,100); print $buffer; print <$fh>; $fh->close; DESCRIPTION
FileHandle::Unget operates exactly the same as FileHandle, except that it provides a version of ungetc that allows you to unget more than one character. It also provides ungets to unget a string. This module is useful if the filehandle refers to a stream for which you can't just "seek()" backwards. Some operating systems support multi-byte "ungetc()", but this is not guaranteed. Use this module if you want a portable solution. In addition, on some operating systems, eof() will not be reset if you ungetc after having read to the end of the file. NOTE: Using "sysread()" with "ungetc()" and other buffering functions is still a bad idea. METHODS
The methods for this package are the same as those of the FileHandle package, with the following exceptions. new ( ARGS ) The constructor is exactly the same as that of FileHandle, except that you can also call it with an existing IO::Handle object to "attach" unget semantics to a pre-existing handle. $fh->ungetc ( ORD ) Pushes a character with the given ordinal value back onto the given handle's input stream. This method can be called more than once in a row to put multiple values back on the stream. Memory usage is equal to the total number of bytes pushed back. $fh->ungets ( BUF ) Pushes a buffer back onto the given handle's input stream. This method can be called more than once in a row to put multiple buffers of characters back on the stream. Memory usage is equal to the total number of bytes pushed back. The buffer is not processed in any way--managing end-of-line characters and whatnot is your responsibility. $fh->buffer ( [BUF] ) Get or set the pushback buffer directly. $fh->input_record_separator ( STRING ) Get or set the per-filehandle input record separator. After it is called, the input record separator for the filehandle is independent of the global $/. Until this method is called (and after clear_input_record_separator is called) the global $/ is used. $fh->clear_input_record_separator () Clear the per-filehandle input record separator. This removes the per-filehandle input record separator semantics, reverting the filehandle to the normal global $/ semantics. tell ( $fh ) "tell" returns the actual file position minus the length of the unget buffer. If you read three bytes, then unget three bytes, "tell" will report a file position of 0. Everything works as expected if you are careful to unget the exact same bytes which you read. However, things get tricky if you unget different bytes. First, the next bytes you read won't be the actual bytes on the filehandle at the position indicated by "tell". Second, "tell" will return a negative number if you unget more bytes than you read. (This can be problematic since this function returns -1 on error.) seek ( $fh, [POSITION], [WHENCE] ) "seek" defaults to the standard seek if possible, clearing the unget buffer if it succeeds. If the standard seek fails, then "seek" will attempt to seek within the unget buffer. Note that in this case, you will not be able to seek backward--FileHandle::Unget will only save a buffer for the next bytes to be read. For example, let's say you read 10 bytes from a pipe, then unget the 10 bytes. If you seek 5 bytes forward, you won't be able to read the first five bytes. (Otherwise this module would have to keep around a lot of probably useless data!) COMPATIBILITY
To test that this module is indeed a drop-in replacement for FileHandle, the following modules were modified to use FileHandle::Unget, and tested using "make test". They have all passed. BUGS
There is a bug in Perl on Windows that is exposed if you open a stream, then check for eof, then call binmode. For example: # First line # Second line open FH, "$^X -e "open F, '$0';binmode STDOUT;print <F>" |"; eof(FH); binmode(FH); print "First line:", scalar <FH>, " "; print "Second line:", scalar <FH>, " "; close FH; One solution is to make sure that you only call binmode immediately after opening the filehandle. I'm not aware of any workaround for this bug that FileHandle::Unget could implement. However, the module does detect this situation and prints a warning. Contact david@coppit.org for bug reports and suggestions. AUTHOR
David Coppit <david@coppit.org>. LICENSE
This software is distributed under the terms of the GPL. See the file "LICENSE" for more information. SEE ALSO
Mail::Mbox::MessageParser for an example of how to use this package. perl v5.12.1 2009-08-09 FileHandle::Unget(3)
All times are GMT -4. The time now is 02:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy