Richard Sargent wrote
> In many Smalltalk implementations, there are (at least) three behaviours
> for this kind of thing: #storeString, #printString, and #displayString. I
> would argue against conflating them.
+1. There was a reason we added the "File @" prefix (although I don't
remember the
stepharo wrote
> about
> https://pharo.fogbugz.com/f/cases/18956/FileReference-printString-should-be-auto-evaluable
>
>
> 'tmp/foo.txt' asFileReference
> >
> File @ tmp/foo.txt
>
> and it would be much much better to get back
> 'tmp/foo.txt' asFileReference
>
> So that we can get
> {
about
https://pharo.fogbugz.com/f/cases/18956/FileReference-printString-should-be-auto-evaluable
'tmp/foo.txt' asFileReference
>
File @ tmp/foo.txt
and it would be much much better to get back
'tmp/foo.txt' asFileReference
So that we can get
{ 'tmp/foo.txt' asFileReference }
> {
