in reply to Re^5: Should Modules Do I/O?
in thread Should Modules Do I/O?

As you acknowledge, these three interfaces can be implemented using eachother.
I did not acknowledge that--I flat out contradicted it ... And I'm not sure how you came to that reading from my post?

I was talking about this sentence:

With the interface I describe, the other two interfaces can be trivially derived through subclassing, or just simple procedural wrappers.

What you call trivially derived is what I meant when I said implemented using eachother. Just to make it even more clear, I meant you can make the filehandle interface, and have the other interfaces use that.

If there are common usage scenarios that would benefit from a simpler interface, these should be provided through a separate package that wraps the flexible interface

This is six of one or half dozen of the other. If you insist on moving the simple interfaces into a ::Simple module, so be it. But it should be made from the beginning, otherwise there will be users who end up writing code they shouldn't have to write.

Frankly, I think that the more good interfaces there are available, the better. It can be done cleanly, and it can be done without "adding bloat to a module." Your position on this matter flies in the face of my years of experience using Perl.

PS: I will not reply any further. I have said about all I can on this subject. Please feel free to respond, but don't expect me to.