I didn't think about danger because it is a short term hack that will go away soon. I was just wondering because I think it is a bug.
I now compile storeString into the method which generates an ordered collection. Norbert > Am 19.02.2016 um 10:46 schrieb Sven Van Caekenberghe <s...@stfx.eu>: > > But I think it is a bit dangerous to rely on a specific EOL convention being > maintained in method source code. Although I agree that it should not touch > the contents of constants. > > You could do something (inefficient) like > > ^ String lf join: 'one > two > three' lines > > I've done this before (to get CRLF). > >> On 19 Feb 2016, at 10:32, Marcus Denker <marcus.den...@inria.fr> wrote: >> >> Hi, >> >> This is strange… do you have a way to re-create it? >> >> it looks like a bug (or a non-wanted side effect) to me... >>> On 17 Feb 2016, at 09:56, Norbert Hartl <norb...@hartl.name> wrote: >>> >>> I had a strange effect using a method as storage. I had a list of strings >>> that I compiled into a method. The strings were delimited by Character lf. >>> I created this on a Mac. Saving the source and opening the same code on a >>> linux machine changed the line endings from lf to cr. >>> IMHO this is a bug because I think that the content of a method should be >>> unchanged in that case. Or are there any other reasons why this is the way >>> it is? >>> >>> thanks, >>> >>> Norbert >>> >>> >> >> > >
