the standard string representation of an abstract platform independent representation of a file should be that: abstract & platform independent (it would be terrible to mask that behind a platform dependent external representation)
furthermore it makes sense that the print string gives an indication of what it actually is/models: hence it is useful to add the type reference (else totally different ones will look the same) there are other accessors that do what you want, why can't you use those ? most objects cannot come up with just one single canonical representation for example, according to universal standards, ZnUrl and ZnMimeType can do this, but these are exceptions > On 10 Mar 2015, at 16:47, Sebastian Sastre <sebast...@flowingconcept.com> > wrote: > > >> On Mar 10, 2015, at 8:43 AM, Sven Van Caekenberghe <s...@stfx.eu> wrote: >> >> OK, both of the following make sense >> >> /Users/sven/Desktop/foo.txt >> file:///Users/sven/Desktop/foo.txt >> >> But what about native (OS platform) conventions ? >> >> I don't want to see Windows backslashes, but Windows user might disagree. >> >> There is not one good solution, hence you must use specific >> accessors/convertors. > > The alternative to no one good solution is to find the sensible less worst > solution. > > Do we have a way to strategise the answer of asString per supported platform > in such a way that it will conform the string representation of the path to a > file? > > I’m still trying to understand the practical use of the current answer > instead of strategize the answer per platform
