in reply to seeking help for seek function

Why do you use sysseek instead of seek? All the functions beginning with sys are for unbuffered IO, whereas readline is buffered IO. The docs warn against mixing those.
Perl 6 - links to (nearly) everything that is Perl 6.

Replies are listed 'Best First'.
Re^2: seeking help for seek function
by Anonymous Monk on Mar 25, 2010 at 08:58 UTC
    seek prints 1 (true), only sysseek prints the position. can you please tell me how i can print the line from the file if i use seek?
[reply]

      If you want to know the position, use tell. If you want to set the position, use seek.

[reply]
Re^2: seeking help for seek function
by pearly (Initiate) on Mar 25, 2010 at 09:01 UTC
    seek prints 1 (true), only sysseek prints the position. can you please tell me how i can print the line from the file if i use seek?
[reply]
      sysseek and seek do not print anything, it is you calling print. Those functions set the file position, they do not read the file (as others have said).

      Looking at your code - forgive me if I am wrong here - you seem to be getting the file positions from the first file and using those same positions to find records in the second file. Unless each file has corresponding records of exactly the same length, then that will not work. tell and sysseek give the current byte offset position in the current file, that position will not (usually) apply to another file unless it is exactly the same format.
[reply]
        hi, thanks for your reply. Actually, i am getting the file position from the first file and find records in the first file too. I am using the second file, only to know which record i should fetch based on the id given in second file. Thus i am matching the id's from the second file to the first file. The second file is important for the cluster headings.Thanks !!!
[reply]

In Section Seekers of Perl Wisdom