Glenn McAllister wrote: > > I'm with Stefan on this one. �I'm not a big fan of "candy machine" > interfaces that depend on a flag to control behaviour. �The name > copyFile implies that its job is to copy a file, not to check if > the new file already exists and should only be overwritten if the > original file is newer. �If you want that behaviour, create a > copyFileIfNewer method that has the same signature, does the > appropriate checking, then calls copyFile. Its cleaner and keeps > the intent of the method clear.
Just curious, what does javac imply to you? My feeling is that all tasks should be "smart" unless otherwise and explicitly stated. Whether that explicit designation goes into the name of the entity or into an attribute doesn't much matter to me. - Sam Ruby
