[Pharo-dev] Just found, i can compile this:

extent: newExtent vertical ifTrue: [ newExtent := self defaultWidth @ newExtent y ] ifFalse: [ newExtent := newExtent x @ self defaultWidth ]. super extent: newExtent Can you verify it? Arguments should be not assignable. -- Best regards, Igor Stasenko.

Re: [Pharo-dev] Just found, i can compile this:

Indeed, I can compile: C>>foo: arg ^ arg := 3 And 'C new foo: 1' returns 3... On 18 mars 2014, at 15:16, Igor Stasenko wrote: > extent: newExtent > > vertical > ifTrue: [ newExtent := self defaultWidth @ newExtent y ] > ifFalse: [ newExtent := newExtent x @

Re: [Pharo-dev] Just found, i can compile this:

similiar to issue 12419 block arguments should be read only 2014-03-18 15:21 GMT+01:00 Camille Teruel : > Indeed, I can compile: > > C>>foo: arg > ^ arg := 3 > > And 'C new foo: 1' returns 3... > > > On 18 mars 2014, at 15:16, Igor Stasenko

Re: [Pharo-dev] Just found, i can compile this:

Hello, For blockClosures it is normal, block closure arguments have always been assignable since smalltalk-80. We could add a warning to discourage it, but we cannot forbid it, or we will not be able to load lots of frameworks and libraries that use it. So 12419

Re: [Pharo-dev] Just found, i can compile this:

Why arguments should be read only? They are just temporary variables with an initial value. > 2014-03-18 15:45 GMT+01:00 Nicolai Hess : > similiar to issue 12419 block arguments should be read only > > > 2014-03-18 15:21 GMT+01:00 Camille Teruel : > > Indeed, I can compile: > > C>>foo: arg >

Re: [Pharo-dev] Just found, i can compile this:

On 18 mars 2014, at 17:02, Clément Bera wrote: > Hello, > > For blockClosures it is normal, block closure arguments have always been > assignable since smalltalk-80. I never noticed, that's a weird 'feature'. > We could add a warning to discourage it, but we cannot forbid it, or we will > n

Re: [Pharo-dev] Just found, i can compile this:

On 18.03.2014, at 18:17, Camille Teruel wrote: > > On 18 mars 2014, at 17:02, Clément Bera wrote: > >> Hello, >> >> For blockClosures it is normal, block closure arguments have always been >> assignable since smalltalk-80. > > I never noticed, that's a weird 'feature'. > >> We could add a

Re: [Pharo-dev] Just found, i can compile this:

2014-03-18 18:31 GMT+01:00 Max Leske : > > On 18.03.2014, at 18:17, Camille Teruel wrote: > > > On 18 mars 2014, at 17:02, Clément Bera wrote: > > Hello, > > For blockClosures it is normal, block closure arguments have always been > assignable since smalltalk-80. > > > I never noticed, that's a

Re: [Pharo-dev] Just found, i can compile this:

2014-03-18 18:47 GMT+01:00 Clément Bera : > 2014-03-18 18:31 GMT+01:00 Max Leske : > > >> On 18.03.2014, at 18:17, Camille Teruel wrote: >> >> >> On 18 mars 2014, at 17:02, Clément Bera wrote: >> >> Hello, >> >> For blockClosures it is normal, block closure arguments have always been >> assignab

Re: [Pharo-dev] Just found, i can compile this:

On Tue, Mar 18, 2014 at 10:10 AM, Christophe Demarey < christophe.dema...@inria.fr> wrote: > Why arguments should be read only? > They are just temporary variables with an initial value. > Read the blue book. It was a decision of the language designers to forbid assignment to arguments to allow

Re: [Pharo-dev] Just found, i can compile this:

Hi Clément, On Tue, Mar 18, 2014 at 9:02 AM, Clément Bera wrote: > Hello, > > For blockClosures it is normal, block closure arguments have always been > assignable since smalltalk-80. We could add a warning to discourage it, but > we cannot forbid it, or we will not be able to load lots of frame

Re: [Pharo-dev] Just found, i can compile this:

On 18 Mar 2014, at 17:02, Clément Bera wrote: > Hello, > > For blockClosures it is normal, block closure arguments have always been > assignable since smalltalk-80. No this is wrong. > We could add a warning to discourage it, but we cannot forbid it, or we will > not be able to load lots o

Re: [Pharo-dev] Just found, i can compile this:

Le 18 mars 2014 à 19:50, Eliot Miranda a écrit : > On Tue, Mar 18, 2014 at 10:10 AM, Christophe Demarey > wrote: > Why arguments should be read only? > They are just temporary variables with an initial value. > > Read the blue book. It was a decision of the language designers to forbid > ass

Re: [Pharo-dev] Just found, i can compile this:

Hi Christophe, On Mar 19, 2014, at 1:45 AM, Christophe Demarey wrote: > > Le 18 mars 2014 à 19:50, Eliot Miranda a écrit : > >> On Tue, Mar 18, 2014 at 10:10 AM, Christophe Demarey >> wrote: >>> Why arguments should be read only? >>> They are just temporary variables with an initial value.

Re: [Pharo-dev] Just found, i can compile this:

Hi Eliot, Le 19 mars 2014 à 16:25, Eliot Miranda a écrit : > Hi Christophe, > > On Mar 19, 2014, at 1:45 AM, Christophe Demarey > wrote: > >> >> Le 18 mars 2014 à 19:50, Eliot Miranda a écrit : >> >>> On Tue, Mar 18, 2014 at 10:10 AM, Christophe Demarey >>> wrote: >>> Why arguments should

Re: [Pharo-dev] Just found, i can compile this:

On Thu, Mar 20, 2014 at 2:03 AM, Christophe Demarey < christophe.dema...@inria.fr> wrote: > Hi Eliot, > > Le 19 mars 2014 à 16:25, Eliot Miranda a écrit : > > Hi Christophe, > > On Mar 19, 2014, at 1:45 AM, Christophe Demarey < > christophe.dema...@inria.fr> wrote: > > > Le 18 mars 2014 à 19:50, E

Re: [Pharo-dev] Just found, i can compile this:

On 20 March 2014 17:04, Eliot Miranda wrote: > > > > On Thu, Mar 20, 2014 at 2:03 AM, Christophe Demarey < > christophe.dema...@inria.fr> wrote: > >> Hi Eliot, >> >> Le 19 mars 2014 à 16:25, Eliot Miranda a écrit : >> >> Hi Christophe, >> >> On Mar 19, 2014, at 1:45 AM, Christophe Demarey < >> ch

Re: [Pharo-dev] Just found, i can compile this:

Hi Eliot, Le 20 mars 2014 à 17:04, Eliot Miranda a écrit : > On Thu, Mar 20, 2014 at 2:03 AM, Christophe Demarey > wrote: > Hi Eliot, > > Le 19 mars 2014 à 16:25, Eliot Miranda a écrit : > >> Hi Christophe, >> >> On Mar 19, 2014, at 1:45 AM, Christophe Demarey >> wrote: >> >>> >>> Le 18

Re: [Pharo-dev] Just found, i can compile this:

On Mon, Mar 24, 2014 at 10:00 AM, Christophe Demarey < christophe.dema...@inria.fr> wrote: > Hi Eliot, > > Le 20 mars 2014 à 17:04, Eliot Miranda a écrit : > > On Thu, Mar 20, 2014 at 2:03 AM, Christophe Demarey < > christophe.dema...@inria.fr> wrote: > >> Hi Eliot, >> >> Le 19 mars 2014 à 16:25,