what's wrong about this chomp code?

Z

Zhenning Guan

when I was running this code
------------
File.open("1c.txt") do |f|
while line= f.gets.chomp;
p line ;
end
end
-------------

why they warning with the message below?

=========
private method 'chomp' called for nil:NilClass <nomethoderror>
from ok.rb:2:in 'open'
from ok.rb:2
==========
 
S

Stefano Crocco

Alle Wednesday 05 November 2008, Zhenning Guan ha scritto:
when I was running this code
------------
File.open("1c.txt") do |f|
while line= f.gets.chomp;
p line ;
end
end
-------------

why they warning with the message below?

=========
private method 'chomp' called for nil:NilClass <nomethoderror>
from ok.rb:2:in 'open'
from ok.rb:2
==========

Because chomp will be called on the value returned by f.gets, even when it's
nil. You need to move the call to chomp inside the while loop:

while line=f.gets
line = line.chomp #or simply line.chomp!
...

You can also add a rescue clause inside the condition of the while loop:

while (line = f.gets.chomp rescue nil)
...

This way, when f.gets returns nil and the NoMethodError exception is raised,
the exception is rescued and line is set to nil, which causes the loop to end.

I hope this helps

Stefano
 
Z

Zhenning Guan

Stefano said:
This way, when f.gets returns nil and the NoMethodError exception is
raised,
the exception is rescued and line is set to nil, which causes the loop
to end.

I hope this helps

Stefano

Thank you for help me understand it. :)
 
L

Lloyd Linklater

Zhenning said:
when I was running this code
------------
File.open("1c.txt") do |f|
while line= f.gets.chomp;
p line ;
end
end
-------------

why they warning with the message below?

=========
private method 'chomp' called for nil:NilClass <nomethoderror>
from ok.rb:2:in 'open'
from ok.rb:2
==========


This might be easier:
File.open('1c.txt').each { |line| puts line.chomp }
 
S

Sebastian Hungerecker

Lloyd said:
File.open('1c.txt').each { |line| puts line.chomp }

File.foreach('1c.txt') {|line| puts line}

File.foreach is better than File.open(...).each because that way the file is
closed right away (with your code open returns a file object that you simply
throw away after calling each on it, so you can't call close on it). And
doing puts file.chomp is pointless as puts will just readd the \n removed by
chomp.

HTH,
Sebastian
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,999
Messages
2,570,243
Members
46,835
Latest member
lila30

Latest Threads

Top