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 :
>
> But I thin
Or be platform-independent and store it in an array, and retrieve on demand?
MyStorage>>strings
^ #('string1' 'string2' 'string3' ...)
MyStorage>>stringsSeparated
^ self stringsSeparatedBy: String lf
MyStorage>>stringsSeparatedBy: aSeparator
^ self string joinUsing: aSeparator
On F
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 CR
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 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 de
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
