- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Are assignment to block variables is prohibited?

by Marcus Denker

> On 14 Sep 2017, at 22:00, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2017-09-14 21:43 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>>: > Yes. But there is a setting for the compiler to load/compile code with errors. > > > 2017-09-14 20:46 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>>: > Hi > > I know that method arg are read only and you cannot assign to them. > Now what is the status of block arguments? > Because some old code of plotmorph is breaking. > > Stef > > > > But using catalog, I can load plotmorph, even without enabling this setting. OCStoreIntoReadOnlyVariableError checks if you are compiling interactively or not. signal compilationContext interactive ifFalse: [ ^ self crTrace ]. ^ super signal This way old code load fine, but you are not allowed to create such code while codingâ¦ and you have to fix code when recompiling a method interactively that has an assignment to an argument. Marcus

Sept. 15, 2017

Re: [Pharo-dev] Are assignment to block variables is prohibited?

by Nicolai Hess

2017-09-14 21:43 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: > Yes. But there is a setting for the compiler to load/compile code with > errors. > > > 2017-09-14 20:46 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > >> Hi >> >> I know that method arg are read only and you cannot assign to them. >> Now what is the status of block arguments? >> Because some old code of plotmorph is breaking. >> >> Stef >> >> But using catalog, I can load plotmorph, even without enabling this setting.

Sept. 14, 2017

Re: [Pharo-dev] Are assignment to block variables is prohibited?

by Nicolai Hess

Yes. But there is a setting for the compiler to load/compile code with errors. 2017-09-14 20:46 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Hi > > I know that method arg are read only and you cannot assign to them. > Now what is the status of block arguments? > Because some old code of plotmorph is breaking. > > Stef > >

Sept. 14, 2017

Re: [Pharo-dev] [Calypso] Toolbar and Statusbar Look - voting time

by Torsten Bergmann

"Denis Kudriashov" wrote >Thank's guys for comments. And thank's Torsten for this initiative.Â I will merge your changes soon. No - we have to thank you. For Calypso, for accepting the community decision and (in advance) for merging the first Calypso pull request. I'm pretty sure the next Pharo versions will rock even more ... Bye T.

Sept. 14, 2017

Re: [Pharo-dev] Author name in version Iceberg?

by Peter UhnÃ¡k

For FileTree using log should be enough to get the authorship. For tonel you need blame. On Thu, Sep 14, 2017 at 8:47 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > ahhhh > ok but still we need help because our todo list is long. > > > On Thu, Sep 14, 2017 at 8:37 PM, stephan <stephan(a)stack.nl> wrote: > > On 14-09-17 20:05, Stephane Ducasse wrote: > >> > >> We worked during years without blame. If you tell me I have a long > >> list of more important items for esteban: > > > > ... > > > >> In fact our list is huge and I do not see blame. > > > > > > The thing is just to use blame to extract the author information. > > I guess it is the easiest way to get that out of git without storing the > > timestamp. > > > > Stephan > > > > > > > >

Sept. 14, 2017

Re: [Pharo-dev] Sources location and name, PharoLauncher

by Pavel Krivanek

2017-09-14 15:10 GMT+02:00 stephan <stephan(a)stack.nl>: > On 14-09-17 14:52, Peter UhnÃ¡k wrote: > >> That's not related to Pharo Launcher. Pharo 7 sources (for alpha images) >> are now shipped with the image, not the VM. >> > > That's an issue. I have hundreds of images, and definitely don't need so > many different sources. You can share sources for as many images as you want as soon these images are based on the same bootstrapped image build. -- Pavel > > > Stephan > > >

Sept. 14, 2017

Re: [Pharo-dev] Author name in version Iceberg?

by Stephane Ducasse

ahhhh ok but still we need help because our todo list is long. On Thu, Sep 14, 2017 at 8:37 PM, stephan <stephan(a)stack.nl> wrote: > On 14-09-17 20:05, Stephane Ducasse wrote: >> >> We worked during years without blame. If you tell me I have a long >> list of more important items for esteban: > > ... > >> In fact our list is huge and I do not see blame. > > > The thing is just to use blame to extract the author information. > I guess it is the easiest way to get that out of git without storing the > timestamp. > > Stephan > > >

Sept. 14, 2017

Are assignment to block variables is prohibited?

by Stephane Ducasse

Hi I know that method arg are read only and you cannot assign to them. Now what is the status of block arguments? Because some old code of plotmorph is breaking. Stef

Sept. 14, 2017

Re: [Pharo-dev] Author name in version Iceberg?

by stephan

On 14-09-17 20:05, Stephane Ducasse wrote: > We worked during years without blame. If you tell me I have a long > list of more important items for esteban: ... > In fact our list is huge and I do not see blame. The thing is just to use blame to extract the author information. I guess it is the easiest way to get that out of git without storing the timestamp. Stephan

Sept. 14, 2017

Re: [Pharo-dev] Sources location and name, PharoLauncher

by stephan

On 14-09-17 20:00, Stephane Ducasse wrote: > Kill some images :). > We did that for good reasons I do not remember why but this is due to > the bootstrap. > Stefan we will never be perfect day one. This is not possible for us. Don't worry. Break it to improve it. I have to change my workflow, so I am running into lots of things. Stephan

Sept. 14, 2017