• Home
• Syllabus
• Schedule
• Checkin
• Homework
  • HW0
  • HW1
  • HW2
  • HW3
  • HW4
  • HW5
  • HW6
  • HW7
• Piazza
• Slides
• Other Info

I/O Lab                

Description                

In this lab, we’ll do some exercises with I/O streams. The files for this lab are available in ~cs253/Labs/IO. You will modify code in these files.                 

Robust input operators                

Consider number.cc. It creates a class called Number that’s a wrapper around an int.                 

1. How is it that << works for Number, even though operator<< wasn’t defined for this class?
2. Consider operator>>. It doesn’t check for failure. And, yet, it works properly for:
   • valid numeric input
   • end of input
   • incorrect input
   How can this be?
3. Now, improve operator>> so that it works properly for input such as “one”, “two”, “three”, “four”, and “five”, as well as working for all traditional numeric input that worked before.
   • Consider using «ios::clear(cpp)»
4. Show your result at this stage.

Using fstream to modify a file in place.                

Consider modify.cc. It copies its input file to its output file, replacing all instances of “global” with “denial”.                 

Note the use of getline. There are two versions of this function:

• The free function getline reads into a C++ string.
• «istream::getline(cpp)» reads into a C-style character array.

Change modify.cc to modify a single file in place. That is, the program should only take a single filename argument.                 

Hints:

1. If you read the entire file into one giant string, you’re doing it wrong. Your code should work for colossal files that don’t fit into memory.
2. What sort of open mode should you use?
3. This approach only works if the replacement string is the same length as the original string. However, it sure is efficient.
4. Also show the result at this stage.

For extra fame & glory                

Improve operator>> in number.cc even more:
If it encounters invalid input such as “zork”, it shouldn’t consume the bogus input. It should fail, and leave things such that the next read (assuming that the stream is put back into a good state) would see “zork” again.                 

User: Guest                 

Apply to CSU | Contact CSU | Disclaimer | Equal Opportunity
Colorado State University, Fort Collins, CO 80523 USA
© 2018 Colorado State University