2010/1/12 Levente Uzonyi <[hidden email]>:
> On Mon, 11 Jan 2010, Nicolas Cellier wrote: > >> Hi Levente, >> what about completely ignoring line endings in diffs ? >> > > I intentionally added this feature. Do you think it's wrong? > > IMO empty lines (and white space in general), is not an informal part of source code, so diffing them makes not much sense. > Levente > >> split: aString >> "I return an Array of strings which are the lines extracted from >> aString. All lines contain the line separator characters" >> >> ^Array streamContents: [ :stream | >> aString lineIndicesDo: [ :start :endWithoutSeparators :end >> | >> stream nextPut: (aString copyFrom: start to: >> endWithoutSeparators) ] ] >> >> or simply >> >> >> split: aString >> "I return an Array of strings which are the lines extracted from >> aString. All lines contain the line separator characters" >> >> ^Array streamContents: [ :stream | >> aString linesDo: [ :aLineWithoutEnding | >> stream nextPut: aLineWithoutEnding ] ] >> >> Nicolas >> >> 2010/1/11 Andreas Raab <[hidden email]>: >>> >>> Levente Uzonyi wrote: >>>> >>>> On Sun, 10 Jan 2010, Andreas Raab wrote: >>>>> >>>>> I think I'll leave that decision to you, you seem to have a good handle >>>>> on this part of the system. FWIW, I had implemented option #2 for our >>>>> SqueakSource installation realizing that it would be robust even if we >>>>> decided to leave out the CRs from the diff. >>>> >>>> With the latest TextDiffBuilder changes everything should work fine with >>>> all versions of SqueakSource. #buildTextPatch is SqueakSource's >>>> extension >>>> method, changing that would break backwards compatibility. >>> >>> Yup, agreed. It was a quick localized fix for our installation. I didn't >>> feel like messing around with TextDiffBuilder itself - making the change >>> in >>> the one extension method felt safer for our purposes. Thanks for fixing >>> the >>> issue at the root! >>> >>> Cheers, >>> - Andreas >>> >>> >> > > > > -- Best regards, Igor Stasenko AKA sig. |
On Tue, 12 Jan 2010, Igor Stasenko wrote:
> 2010/1/12 Levente Uzonyi <[hidden email]>: >> On Mon, 11 Jan 2010, Nicolas Cellier wrote: >> >>> Hi Levente, >>> what about completely ignoring line endings in diffs ? >>> >> >> I intentionally added this feature. Do you think it's wrong? >> >> > IMO empty lines (and white space in general), is not an informal part > of source code, > so diffing them makes not much sense. accidentally added some linefeeds while pasting code from and external source. The diff shows no changes. Is that OK? Levente > >> Levente >> >>> split: aString >>> "I return an Array of strings which are the lines extracted from >>> aString. All lines contain the line separator characters" >>> >>> ^Array streamContents: [ :stream | >>> aString lineIndicesDo: [ :start :endWithoutSeparators :end >>> | >>> stream nextPut: (aString copyFrom: start to: >>> endWithoutSeparators) ] ] >>> >>> or simply >>> >>> >>> split: aString >>> "I return an Array of strings which are the lines extracted from >>> aString. All lines contain the line separator characters" >>> >>> ^Array streamContents: [ :stream | >>> aString linesDo: [ :aLineWithoutEnding | >>> stream nextPut: aLineWithoutEnding ] ] >>> >>> Nicolas >>> >>> 2010/1/11 Andreas Raab <[hidden email]>: >>>> >>>> Levente Uzonyi wrote: >>>>> >>>>> On Sun, 10 Jan 2010, Andreas Raab wrote: >>>>>> >>>>>> I think I'll leave that decision to you, you seem to have a good handle >>>>>> on this part of the system. FWIW, I had implemented option #2 for our >>>>>> SqueakSource installation realizing that it would be robust even if we >>>>>> decided to leave out the CRs from the diff. >>>>> >>>>> With the latest TextDiffBuilder changes everything should work fine with >>>>> all versions of SqueakSource. #buildTextPatch is SqueakSource's >>>>> extension >>>>> method, changing that would break backwards compatibility. >>>> >>>> Yup, agreed. It was a quick localized fix for our installation. I didn't >>>> feel like messing around with TextDiffBuilder itself - making the change >>>> in >>>> the one extension method felt safer for our purposes. Thanks for fixing >>>> the >>>> issue at the root! >>>> >>>> Cheers, >>>> - Andreas >>>> >>>> >>> >> >> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > |
2010/1/12 Levente Uzonyi <[hidden email]>:
> On Tue, 12 Jan 2010, Igor Stasenko wrote: > >> 2010/1/12 Levente Uzonyi <[hidden email]>: >>> >>> On Mon, 11 Jan 2010, Nicolas Cellier wrote: >>> >>>> Hi Levente, >>>> what about completely ignoring line endings in diffs ? >>>> >>> >>> I intentionally added this feature. Do you think it's wrong? >>> >>> >> IMO empty lines (and white space in general), is not an informal part >> of source code, >> so diffing them makes not much sense. > > Imagine that you removed lf characters from the code or you accidentally > added some linefeeds while pasting code from and external source. The diff > shows no changes. Is that OK? > To me, it's OK since different lineEnding are now rendered the same. Unless the difference is important for exporting code? Nicolas > > Levente > >> >>> Levente >>> >>>> split: aString >>>> "I return an Array of strings which are the lines extracted from >>>> aString. All lines contain the line separator characters" >>>> >>>> ^Array streamContents: [ :stream | >>>> aString lineIndicesDo: [ :start :endWithoutSeparators >>>> :end >>>> | >>>> stream nextPut: (aString copyFrom: start to: >>>> endWithoutSeparators) ] ] >>>> >>>> or simply >>>> >>>> >>>> split: aString >>>> "I return an Array of strings which are the lines extracted from >>>> aString. All lines contain the line separator characters" >>>> >>>> ^Array streamContents: [ :stream | >>>> aString linesDo: [ :aLineWithoutEnding | >>>> stream nextPut: aLineWithoutEnding ] ] >>>> >>>> Nicolas >>>> >>>> 2010/1/11 Andreas Raab <[hidden email]>: >>>>> >>>>> Levente Uzonyi wrote: >>>>>> >>>>>> On Sun, 10 Jan 2010, Andreas Raab wrote: >>>>>>> >>>>>>> I think I'll leave that decision to you, you seem to have a good >>>>>>> handle >>>>>>> on this part of the system. FWIW, I had implemented option #2 for our >>>>>>> SqueakSource installation realizing that it would be robust even if >>>>>>> we >>>>>>> decided to leave out the CRs from the diff. >>>>>> >>>>>> With the latest TextDiffBuilder changes everything should work fine >>>>>> with >>>>>> all versions of SqueakSource. #buildTextPatch is SqueakSource's >>>>>> extension >>>>>> method, changing that would break backwards compatibility. >>>>> >>>>> Yup, agreed. It was a quick localized fix for our installation. I >>>>> didn't >>>>> feel like messing around with TextDiffBuilder itself - making the >>>>> change >>>>> in >>>>> the one extension method felt safer for our purposes. Thanks for fixing >>>>> the >>>>> issue at the root! >>>>> >>>>> Cheers, >>>>> - Andreas >>>>> >>>>> >>>> >>> >>> >>> >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > > > |
In reply to this post by Levente Uzonyi-2
2010/1/12 Levente Uzonyi <[hidden email]>:
> On Tue, 12 Jan 2010, Igor Stasenko wrote: > >> 2010/1/12 Levente Uzonyi <[hidden email]>: >>> >>> On Mon, 11 Jan 2010, Nicolas Cellier wrote: >>> >>>> Hi Levente, >>>> what about completely ignoring line endings in diffs ? >>>> >>> >>> I intentionally added this feature. Do you think it's wrong? >>> >>> >> IMO empty lines (and white space in general), is not an informal part >> of source code, >> so diffing them makes not much sense. > > Imagine that you removed lf characters from the code or you accidentally > added some linefeeds while pasting code from and external source. The diff > shows no changes. Is that OK? > If the new lines is informal part of source code, i.e. belong to the string literal: foo := '1 2 3 4 '. Then we should care. Otherwise not. > > Levente > >> >>> Levente >>> >>>> split: aString >>>> "I return an Array of strings which are the lines extracted from >>>> aString. All lines contain the line separator characters" >>>> >>>> ^Array streamContents: [ :stream | >>>> aString lineIndicesDo: [ :start :endWithoutSeparators >>>> :end >>>> | >>>> stream nextPut: (aString copyFrom: start to: >>>> endWithoutSeparators) ] ] >>>> >>>> or simply >>>> >>>> >>>> split: aString >>>> "I return an Array of strings which are the lines extracted from >>>> aString. All lines contain the line separator characters" >>>> >>>> ^Array streamContents: [ :stream | >>>> aString linesDo: [ :aLineWithoutEnding | >>>> stream nextPut: aLineWithoutEnding ] ] >>>> >>>> Nicolas >>>> >>>> 2010/1/11 Andreas Raab <[hidden email]>: >>>>> >>>>> Levente Uzonyi wrote: >>>>>> >>>>>> On Sun, 10 Jan 2010, Andreas Raab wrote: >>>>>>> >>>>>>> I think I'll leave that decision to you, you seem to have a good >>>>>>> handle >>>>>>> on this part of the system. FWIW, I had implemented option #2 for our >>>>>>> SqueakSource installation realizing that it would be robust even if >>>>>>> we >>>>>>> decided to leave out the CRs from the diff. >>>>>> >>>>>> With the latest TextDiffBuilder changes everything should work fine >>>>>> with >>>>>> all versions of SqueakSource. #buildTextPatch is SqueakSource's >>>>>> extension >>>>>> method, changing that would break backwards compatibility. >>>>> >>>>> Yup, agreed. It was a quick localized fix for our installation. I >>>>> didn't >>>>> feel like messing around with TextDiffBuilder itself - making the >>>>> change >>>>> in >>>>> the one extension method felt safer for our purposes. Thanks for fixing >>>>> the >>>>> issue at the root! >>>>> >>>>> Cheers, >>>>> - Andreas >>>>> >>>>> >>>> >>> >>> >>> >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > > > -- Best regards, Igor Stasenko AKA sig. |
On Tue, 12 Jan 2010, Igor Stasenko wrote:
> 2010/1/12 Levente Uzonyi <[hidden email]>: >> On Tue, 12 Jan 2010, Igor Stasenko wrote: >> >>> 2010/1/12 Levente Uzonyi <[hidden email]>: >>>> >>>> On Mon, 11 Jan 2010, Nicolas Cellier wrote: >>>> >>>>> Hi Levente, >>>>> what about completely ignoring line endings in diffs ? >>>>> >>>> >>>> I intentionally added this feature. Do you think it's wrong? >>>> >>>> >>> IMO empty lines (and white space in general), is not an informal part >>> of source code, >>> so diffing them makes not much sense. >> >> Imagine that you removed lf characters from the code or you accidentally >> added some linefeeds while pasting code from and external source. The diff >> shows no changes. Is that OK? >> > > If the new lines is informal part of source code, i.e. belong to the > string literal: > > foo := '1 > 2 > 3 > > 4 > '. > > Then we should care. Otherwise not. one liners like: at: key put: anObject | index assoc | index := self scanFor: key. assoc := array at: index. assoc ifNil: [self atNewIndex: index put: (Association key: key value: anObject)] ifNotNil: [assoc value: anObject]. ^anObject It's much easier to read this one: at: key put: anObject | index assoc | index := self scanFor: key. assoc := array at: index. assoc ifNil: [ self atNewIndex: index put: (Association key: key value: anObject) ] ifNotNil: [ assoc value: anObject ]. ^anObject For me, every whitespace counts in the above method, but the original question was not this, but: Should the diff algorithm care about the line endings or not? Are these three lines identical or not (in a diff): foo bar<cr><lf> foo bar<cr> foo bar<lf> Levente > > >> >> Levente >> >>> >>>> Levente >>>> >>>>> split: aString >>>>> "I return an Array of strings which are the lines extracted from >>>>> aString. All lines contain the line separator characters" >>>>> >>>>> ^Array streamContents: [ :stream | >>>>> aString lineIndicesDo: [ :start :endWithoutSeparators >>>>> :end >>>>> | >>>>> stream nextPut: (aString copyFrom: start to: >>>>> endWithoutSeparators) ] ] >>>>> >>>>> or simply >>>>> >>>>> >>>>> split: aString >>>>> "I return an Array of strings which are the lines extracted from >>>>> aString. All lines contain the line separator characters" >>>>> >>>>> ^Array streamContents: [ :stream | >>>>> aString linesDo: [ :aLineWithoutEnding | >>>>> stream nextPut: aLineWithoutEnding ] ] >>>>> >>>>> Nicolas >>>>> >>>>> 2010/1/11 Andreas Raab <[hidden email]>: >>>>>> >>>>>> Levente Uzonyi wrote: >>>>>>> >>>>>>> On Sun, 10 Jan 2010, Andreas Raab wrote: >>>>>>>> >>>>>>>> I think I'll leave that decision to you, you seem to have a good >>>>>>>> handle >>>>>>>> on this part of the system. FWIW, I had implemented option #2 for our >>>>>>>> SqueakSource installation realizing that it would be robust even if >>>>>>>> we >>>>>>>> decided to leave out the CRs from the diff. >>>>>>> >>>>>>> With the latest TextDiffBuilder changes everything should work fine >>>>>>> with >>>>>>> all versions of SqueakSource. #buildTextPatch is SqueakSource's >>>>>>> extension >>>>>>> method, changing that would break backwards compatibility. >>>>>> >>>>>> Yup, agreed. It was a quick localized fix for our installation. I >>>>>> didn't >>>>>> feel like messing around with TextDiffBuilder itself - making the >>>>>> change >>>>>> in >>>>>> the one extension method felt safer for our purposes. Thanks for fixing >>>>>> the >>>>>> issue at the root! >>>>>> >>>>>> Cheers, >>>>>> - Andreas >>>>>> >>>>>> >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > |
2010/1/12 Levente Uzonyi <[hidden email]>:
> On Tue, 12 Jan 2010, Igor Stasenko wrote: > >> 2010/1/12 Levente Uzonyi <[hidden email]>: >>> >>> On Tue, 12 Jan 2010, Igor Stasenko wrote: >>> >>>> 2010/1/12 Levente Uzonyi <[hidden email]>: >>>>> >>>>> On Mon, 11 Jan 2010, Nicolas Cellier wrote: >>>>> >>>>>> Hi Levente, >>>>>> what about completely ignoring line endings in diffs ? >>>>>> >>>>> >>>>> I intentionally added this feature. Do you think it's wrong? >>>>> >>>>> >>>> IMO empty lines (and white space in general), is not an informal part >>>> of source code, >>>> so diffing them makes not much sense. >>> >>> Imagine that you removed lf characters from the code or you accidentally >>> added some linefeeds while pasting code from and external source. The >>> diff >>> shows no changes. Is that OK? >>> >> >> If the new lines is informal part of source code, i.e. belong to the >> string literal: >> >> foo := '1 >> 2 >> 3 >> >> 4 >> '. >> >> Then we should care. Otherwise not. > > I care and we should. Newlines make a difference. I don't want to decode one > liners like: > > at: key put: anObject | index assoc | index := self scanFor: key. assoc := > array at: index. assoc ifNil: [self atNewIndex: index put: (Association key: > key value: anObject)] ifNotNil: [assoc value: anObject]. ^anObject > > It's much easier to read this one: > > at: key put: anObject > > | index assoc | > index := self scanFor: key. > assoc := array at: index. > assoc > ifNil: [ self atNewIndex: index put: (Association key: key value: > anObject) ] > ifNotNil: [ assoc value: anObject ]. > ^anObject > > For me, every whitespace counts in the above method, but the original > question was not this, but: > Should the diff algorithm care about the line endings or not? > Are these three lines identical or not (in a diff): > foo bar<cr><lf> > foo bar<cr> > foo bar<lf> > No. Please, not again. :) All of them should be treated equally. We're talking here about source code, not about binary files. > > Levente > -- Best regards, Igor Stasenko AKA sig. |
In reply to this post by Igor Stasenko
2010/1/12 Igor Stasenko <[hidden email]>:
> 2010/1/12 Levente Uzonyi <[hidden email]>: >> On Tue, 12 Jan 2010, Igor Stasenko wrote: >> >>> 2010/1/12 Levente Uzonyi <[hidden email]>: >>>> >>>> On Mon, 11 Jan 2010, Nicolas Cellier wrote: >>>> >>>>> Hi Levente, >>>>> what about completely ignoring line endings in diffs ? >>>>> >>>> >>>> I intentionally added this feature. Do you think it's wrong? >>>> >>>> >>> IMO empty lines (and white space in general), is not an informal part >>> of source code, >>> so diffing them makes not much sense. >> >> Imagine that you removed lf characters from the code or you accidentally >> added some linefeeds while pasting code from and external source. The diff >> shows no changes. Is that OK? >> > > If the new lines is informal part of source code, i.e. belong to the > string literal: > > foo := '1 > 2 > 3 > > 4 > '. > > Then we should care. Otherwise not. True, there is a "semantic" difference as long as cr lf cr-lf have different semantic. But do they ? Since invisible characters are not an explicit specification robust to future editions, my expectations would be low on such code! My interpretation would be this one: if developer did rely on specific line-endings then she should care to explicitely specify line-endings. If she uses invisible specifications, then it means she just want whatever line-endings. Thus, I would not event bother with line endings inside literals and would tend to say: please use appropriate message (like withSqueakLineEnding) Nicolas > > >> >> Levente >> >>> >>>> Levente >>>> >>>>> split: aString >>>>> "I return an Array of strings which are the lines extracted from >>>>> aString. All lines contain the line separator characters" >>>>> >>>>> ^Array streamContents: [ :stream | >>>>> aString lineIndicesDo: [ :start :endWithoutSeparators >>>>> :end >>>>> | >>>>> stream nextPut: (aString copyFrom: start to: >>>>> endWithoutSeparators) ] ] >>>>> >>>>> or simply >>>>> >>>>> >>>>> split: aString >>>>> "I return an Array of strings which are the lines extracted from >>>>> aString. All lines contain the line separator characters" >>>>> >>>>> ^Array streamContents: [ :stream | >>>>> aString linesDo: [ :aLineWithoutEnding | >>>>> stream nextPut: aLineWithoutEnding ] ] >>>>> >>>>> Nicolas >>>>> >>>>> 2010/1/11 Andreas Raab <[hidden email]>: >>>>>> >>>>>> Levente Uzonyi wrote: >>>>>>> >>>>>>> On Sun, 10 Jan 2010, Andreas Raab wrote: >>>>>>>> >>>>>>>> I think I'll leave that decision to you, you seem to have a good >>>>>>>> handle >>>>>>>> on this part of the system. FWIW, I had implemented option #2 for our >>>>>>>> SqueakSource installation realizing that it would be robust even if >>>>>>>> we >>>>>>>> decided to leave out the CRs from the diff. >>>>>>> >>>>>>> With the latest TextDiffBuilder changes everything should work fine >>>>>>> with >>>>>>> all versions of SqueakSource. #buildTextPatch is SqueakSource's >>>>>>> extension >>>>>>> method, changing that would break backwards compatibility. >>>>>> >>>>>> Yup, agreed. It was a quick localized fix for our installation. I >>>>>> didn't >>>>>> feel like messing around with TextDiffBuilder itself - making the >>>>>> change >>>>>> in >>>>>> the one extension method felt safer for our purposes. Thanks for fixing >>>>>> the >>>>>> issue at the root! >>>>>> >>>>>> Cheers, >>>>>> - Andreas >>>>>> >>>>>> >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > |
2010/1/12 Nicolas Cellier <[hidden email]>:
> 2010/1/12 Igor Stasenko <[hidden email]>: >> 2010/1/12 Levente Uzonyi <[hidden email]>: >>> On Tue, 12 Jan 2010, Igor Stasenko wrote: >>> >>>> 2010/1/12 Levente Uzonyi <[hidden email]>: >>>>> >>>>> On Mon, 11 Jan 2010, Nicolas Cellier wrote: >>>>> >>>>>> Hi Levente, >>>>>> what about completely ignoring line endings in diffs ? >>>>>> >>>>> >>>>> I intentionally added this feature. Do you think it's wrong? >>>>> >>>>> >>>> IMO empty lines (and white space in general), is not an informal part >>>> of source code, >>>> so diffing them makes not much sense. >>> >>> Imagine that you removed lf characters from the code or you accidentally >>> added some linefeeds while pasting code from and external source. The diff >>> shows no changes. Is that OK? >>> >> >> If the new lines is informal part of source code, i.e. belong to the >> string literal: >> >> foo := '1 >> 2 >> 3 >> >> 4 >> '. >> >> Then we should care. Otherwise not. > > True, there is a "semantic" difference as long as cr lf cr-lf have > different semantic. But do they ? > Since invisible characters are not an explicit specification robust to > future editions, my expectations would be low on such code! > My interpretation would be this one: if developer did rely on specific > line-endings then she should care to explicitely specify line-endings. > If she uses invisible specifications, then it means she just want > whatever line-endings. > > Thus, I would not event bother with line endings inside literals and > would tend to say: please use appropriate message (like > withSqueakLineEnding) > +1 . A well-grounded argumentation. > Nicolas > -- Best regards, Igor Stasenko AKA sig. |
In reply to this post by Igor Stasenko
On Tue, 12 Jan 2010, Igor Stasenko wrote:
> 2010/1/12 Levente Uzonyi <[hidden email]>: >> Are these three lines identical or not (in a diff): >> foo bar<cr><lf> >> foo bar<cr> >> foo bar<lf> >> > > No. Please, not again. :) All of them should be treated equally. We're > talking here about source code, > not about binary files. Again? I doubt this question was raised before. We are talking about diffs (at least I am). (About the source code: I don't care how the source code is handled if formatting is preserved. And no, I don't like pretty-printed versions.) Levente > >> >> Levente >> > > > -- > Best regards, > Igor Stasenko AKA sig. > > |
2010/1/12 Levente Uzonyi <[hidden email]>:
> On Tue, 12 Jan 2010, Igor Stasenko wrote: > >> 2010/1/12 Levente Uzonyi <[hidden email]>: >>> >>> Are these three lines identical or not (in a diff): >>> foo bar<cr><lf> >>> foo bar<cr> >>> foo bar<lf> >>> >> >> No. Please, not again. :) All of them should be treated equally. We're >> talking here about source code, >> not about binary files. > > Again? I doubt this question was raised before. We are talking about diffs > (at least I am). There was a lengthly discussion about how to deal with different line ending sequences in editor. You luckily missed it :) > > (About the source code: I don't care how the source code is handled if > formatting is preserved. And no, I don't like pretty-printed versions.) > > > Levente > >> >>> >>> Levente >>> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> > > -- Best regards, Igor Stasenko AKA sig. |
On Tue, 12 Jan 2010, Igor Stasenko wrote:
> 2010/1/12 Levente Uzonyi <[hidden email]>: >> On Tue, 12 Jan 2010, Igor Stasenko wrote: >> >>> 2010/1/12 Levente Uzonyi <[hidden email]>: >>>> >>>> Are these three lines identical or not (in a diff): >>>> foo bar<cr><lf> >>>> foo bar<cr> >>>> foo bar<lf> >>>> >>> >>> No. Please, not again. :) All of them should be treated equally. We're >>> talking here about source code, >>> not about binary files. >> >> Again? I doubt this question was raised before. We are talking about diffs >> (at least I am). > > There was a lengthly discussion about how to deal with different line > ending sequences in editor. > You luckily missed it :) The context is different. This is about diffs, not editors. Levente > >> >> (About the source code: I don't care how the source code is handled if >> formatting is preserved. And no, I don't like pretty-printed versions.) >> >> >> Levente >> >>> >>>> >>>> Levente >>>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >>> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > |
In reply to this post by Levente Uzonyi-2
On Mon, Jan 11, 2010 at 10:43 AM, Levente Uzonyi <[hidden email]> wrote: On Sun, 10 Jan 2010, Andreas Raab wrote: Levente: were did you get this values?? What is "seaside default" ? I see another values in my "seaside default" image. Thanks Mariano Smalltalk |
On Wed, 13 Jan 2010, Mariano Martinez Peck wrote:
> On Mon, Jan 11, 2010 at 10:43 AM, Levente Uzonyi <[hidden email]> wrote: > >> SmalltalkImage current >> vmParameterAt: 5 put: 100000; >> vmParameterAt: 6 put: 35000; >> vmParameterAt: 24 put: 16 * 1024 * 1024; >> vmParameterAt: 25 put: 8 * 1024 * 1024. >> > > > Levente: were did you get this values?? What is "seaside default" ? > > I see another values in my "seaside default" image. > >From SmalltalkImage >> #initializeMemorySettingsProfileSeaSide. What are your defaults? Levente > Thanks > > Mariano > > |
On Wed, Jan 13, 2010 at 4:07 PM, Levente Uzonyi <[hidden email]> wrote:
I don't see that method neither in 2.8 or 3 ... wierd
|
Free forum by Nabble | Edit this page |