From: gabriele renzi <surrender_it@...1.vip.ukl.yahoo.com>
Date: 2004-07-03T02:22:48+09:00
Subject: Re: Extending The File Class

il Fri, 2 Jul 2004 17:39:11 +0200, "Robert Klemme" <bob.news@gmx.net>
ha scritto::


>2) is the worst solution IMHO since File is cross platform but those added
>methods seem to be too special (i.e. only meaningfil on OpenVMS).
>

C:\Documents and Settings\nicola>ruby -e "File.readlink 'f' "
-e:1:in `readlink': The readlink() function is unimplemented on this
machine (No
tImplementedError)
        from -e:1
File already provides non portrable methods, so imo, #2 is ok.

Note that the concept of File itself may not be portable :) 

Would'nt be nice if we had a couple of File subclasses like UnixFile
NTFSFile, Reiser4File, VMSFile.. or maybe mixins?
 This also forces users to avoid non portable assumptions :)