On 14 Dec 2016, at 15:14, Peter Uhnak <i.uhnak@gmail.com> wrote:
On Wed, Dec 14, 2016 at 12:13:09PM +0100, Denis Kudriashov wrote:
2016-12-14 12:05 GMT+01:00 Ben Coman <btc@openinworld.com>:
But perhaps all those extensions for different file types should be a trait to not repeat ourselves?
Problem with trait that you could not add it as class extension. Now you could package your GT support as separate package. But with trait it is not possible.
It would be really nice feature by the way
Ok, so the bottom line is, we could either copy GT behavior to FileLocator, or I can at the end remove the asFileReference.
In either case I still don't understand why the result is different - the arguably more stable one ($HOME) is late-bound, but windows disks that can easily change at runtime are not (i.e. (un)plugging a flash disk)?
My home directory /Users/sven is not your home directory /Users/peter but they are both the logical concept of home directory The C or D drive on Windows are always the C or D drive, even if they are removable/changeable, there is no other way to refer to them - they are the same at both levels of abstraction That is how I would interpret the situation
Peter