The code above could, however, just deal with references to some file handle and not actually read or write the contents (though ReadFile() or WriteFile() would be less-than-ideal names for such functionality).
You're also focusing too much on the example, and missing the greater problem. There are other cases that fit the original problem, such a sending an email (who is the sender and who is the receiver?)
My point is that the high-level concept is not always appropriate. Sometimes it's overkill. Sometimes it's outright wrong.
> sending an email (who is the sender and who is the receiver?)
The sender is already encoded in the message itself in that case. The receiver is specified as a specific SMTP message, last I checked. So this problem wouldn't really apply here.
Even if it did, though, the separated functions would still be useful here:
msg = NewMessageFrom("[email protected]")
AddSubject(msg, "Did you ever hear the tragedy of Darth Plagueis the Wise?")
AddBody(msg, "I thought not. It's not a story the Jedi would tell you.")
Send(msg, "[email protected]")
This is Wrong, with a capital W.
The file copy API is fundamentally different to reading and and then writing the contents of a file.
The "copy" system call on most platforms also:
- Copies metadata such as attributes.
- Copies alternate data streams.
- Preserves advanced features such as sparse files, compression, encryption, BTRFS/ReFS/ZFS integrity settings.
- Can copy externally archived files without restoring them.
- Can copy files server-to-server without transferring the data to the client computer.
- Copies block-by-block instead of all at once, allowing files to be copied that do not fit into memory.
- Copies asynchronously so that reads and writes are overlapped
- Etc...