Initially we thought we'd provide subclasses for different OSes like OpenVMSFileUtils or NetwareFileUtils and would use newFileUtils as a factory method. We never did so, though.
Some of the functionality would be the same among all OSes (like closing streams or reading files completely) and could be static, others like normalizing file names would be OS dependent and had to
be non-static.
But it seems that various methods already do OS-dependent checks; this should work equally well with static methods, right? Since the OS does not change during the VM lifetime (I would hope!) there is no reason to keep any state in a FileUtils instance (you could use static variables if you needed to cache something), so there is no reason to have an instance at all.
-J.
-- Jesse Glick <mailto:[EMAIL PROTECTED]> x22801 NetBeans, Open APIs <http://www.netbeans.org/>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
