Legacy java.io.File and new FileSystems
Michael Hall
hallmike at att.net
Tue Aug 10 12:52:39 PDT 2010
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've just started looking at some of the new jdk7 API's and am unsure
about something.
Is there anyway legacy java.io.File can use a new user provided
FileSystem?
I have seen the argument that it would of been difficult to
impossible to retrofit a lot of the new features to the File class so
it was moved to the Path class.
But is this also true of the FileSystem API?
Is there some way it can be indicated that a legacy java.io.File
instance should use a new alternate FileSystem instead of the
platform provided?
Mike Hall hallmike at att dot net
http://www195.pair.com/mik3hall
http://www195.pair.com/mik3hall/home.html
http://sourceforge.net/projects/macnative
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
iJwEAQECAAYFAkxhrg8ACgkQUvk/ZSaThTLGsgP/Xxt8ETXlvjXLXQ6rVFZNw5f8
ZPdMDA7LEN3X8n8TM4vDBaNFSWu7A2FL/q6wCsQNHIlrrkkDHO8ljzggc+3KOpaz
bNabupsdwCyn95Ib4nKQ3D8kqFl3cigmX9oTS41wjb5BQ+dlwgx0B9sJyFPXPsVJ
iwMCkfJsO58yK/TyMSo=
=H5Jd
-----END PGP SIGNATURE-----
More information about the nio-discuss
mailing list