Re: [Pharo-dev] control flow graph

[Stephane Ducasse]

Yes I know but closing counting closing brackets are easier to do on the AST.
Now I imagine that variable reachability is easier with control flow.
A control flow is an dedicated abstraction over a program. Now people I met
want to use it to support clone detection between different language
because this is an abstraction.
And I'm curious to see what we can do if we have this kind of trees.

stef

On Sat, Feb 24, 2018 at 11:51 AM, Clément Bera  wrote:
> The control flow is just a visualisation, everything can be done without it,
> it's just way more convenient to look at.
>
> On Feb 24, 2018 09:08, "Stephane Ducasse"  wrote:
>>
>> Clement this analysis can be done without a control flow no?
>>
>>
>> On Fri, Feb 23, 2018 at 11:47 AM, Clément Bera 
>> wrote:
>> > I used that in the past on intermediate representations, I feel it is
>> > very
>> > useful to directly edit the code of methods with large control flows
>> > since
>> > when you have many closing brackets ] ] ] ] you never know where to
>> > write
>> > your code. Now it's specific to some use-cases such as algorithms where
>> > you
>> > write methods with large control flows, in most methods due to object
>> > oriented programming convention the control flow is not that big. In
>> > this
>> > context other things could be possible (Smart suggestions to move code
>> > out
>> > of loops, etc.)
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Fri, Feb 23, 2018 at 11:37 AM, Stephane Ducasse
>> > 
>> > wrote:
>> >>
>> >> Hi
>> >>
>> >> I'm experimenting in building a control flow graph of pharo methods
>> >> and I would like to know if you have ideas about what we can do
>> >> with them to support our development environment.
>> >>
>> >> Stef
>> >>
>> >
>> >
>> >
>> > --
>> > Clément Béra
>> > Pharo consortium engineer
>> > https://clementbera.wordpress.com/
>> > Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq
>>
>

Re: [Pharo-dev] Linux installation

[Esteban Lorenzano]

> On 24 Feb 2018, at 16:31, Sean P. DeNigris  wrote:
> 
> Stephane Ducasse-3 wrote
>> how do we record what you did because it should not be lost.
> 
> The documentation part was recorded when we reorganized the installation
> instructions on the Pharo website. The OBS stuff I didn't get very far with
> even though I spent a lot of time. The current effort seems to have
> surpassed what Esteban and I did and be led by a more knowledgeable person
> lol

heh… Holger took over and made it work ;)
now, we need to make it the standard for linux distributions… and that will 
require still a bit more effort :)

Esteban

> 
> 
> 
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
> 

Re: [Pharo-dev] Linux installation

[Sean P. DeNigris]

Stephane Ducasse-3 wrote
> how do we record what you did because it should not be lost.

The documentation part was recorded when we reorganized the installation
instructions on the Pharo website. The OBS stuff I didn't get very far with
even though I spent a lot of time. The current effort seems to have
surpassed what Esteban and I did and be led by a more knowledgeable person
lol



-
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Re: [Pharo-dev] control flow graph

[Tudor Girba]

What kind of visualization would you have in mind?

Doru


> On Feb 24, 2018, at 11:51 AM, Clément Bera  wrote:
> 
> The control flow is just a visualisation, everything can be done without it, 
> it's just way more convenient to look at.
> 
> On Feb 24, 2018 09:08, "Stephane Ducasse"  wrote:
> Clement this analysis can be done without a control flow no?
> 
> 
> On Fri, Feb 23, 2018 at 11:47 AM, Clément Bera  wrote:
> > I used that in the past on intermediate representations, I feel it is very
> > useful to directly edit the code of methods with large control flows since
> > when you have many closing brackets ] ] ] ] you never know where to write
> > your code. Now it's specific to some use-cases such as algorithms where you
> > write methods with large control flows, in most methods due to object
> > oriented programming convention the control flow is not that big. In this
> > context other things could be possible (Smart suggestions to move code out
> > of loops, etc.)
> >
> >
> >
> >
> >
> >
> > On Fri, Feb 23, 2018 at 11:37 AM, Stephane Ducasse 
> > wrote:
> >>
> >> Hi
> >>
> >> I'm experimenting in building a control flow graph of pharo methods
> >> and I would like to know if you have ideas about what we can do
> >> with them to support our development environment.
> >>
> >> Stef
> >>
> >
> >
> >
> > --
> > Clément Béra
> > Pharo consortium engineer
> > https://clementbera.wordpress.com/
> > Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq
> 

--
www.tudorgirba.com
www.feenk.com

"When people care, great things can happen."

Re: [Pharo-dev] control flow graph

[Clément Bera]

The control flow is just a visualisation, everything can be done without
it, it's just way more convenient to look at.

On Feb 24, 2018 09:08, "Stephane Ducasse"  wrote:

> Clement this analysis can be done without a control flow no?
>
>
> On Fri, Feb 23, 2018 at 11:47 AM, Clément Bera 
> wrote:
> > I used that in the past on intermediate representations, I feel it is
> very
> > useful to directly edit the code of methods with large control flows
> since
> > when you have many closing brackets ] ] ] ] you never know where to write
> > your code. Now it's specific to some use-cases such as algorithms where
> you
> > write methods with large control flows, in most methods due to object
> > oriented programming convention the control flow is not that big. In this
> > context other things could be possible (Smart suggestions to move code
> out
> > of loops, etc.)
> >
> >
> >
> >
> >
> >
> > On Fri, Feb 23, 2018 at 11:37 AM, Stephane Ducasse <
> stepharo.s...@gmail.com>
> > wrote:
> >>
> >> Hi
> >>
> >> I'm experimenting in building a control flow graph of pharo methods
> >> and I would like to know if you have ideas about what we can do
> >> with them to support our development environment.
> >>
> >> Stef
> >>
> >
> >
> >
> > --
> > Clément Béra
> > Pharo consortium engineer
> > https://clementbera.wordpress.com/
> > Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq
>
>

[Pharo-dev] [Pharo 7.0-dev] Build #602: 19755-Addition-of-Users-of-it-in-the-Code-Search-menu

[ci-pharo-ci-jenkins2]

There is a new Pharo build available!

The status of the build #602 was: SUCCESS.

The Pull Request #952 was integrated: 
"19755-Addition-of-Users-of-it-in-the-Code-Search-menu"
Pull request url: https://github.com/pharo-project/pharo/pull/952

Issue Url: https://pharo.fogbugz.com/f/cases/19755
Build Url: 
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/602/

[Pharo-dev] Another month of active improvements....

[Stephane Ducasse]

Report period: 21 January 2018 to 24 February 2018

*  19755-Addition-of-Users-of-it-in-the-Code-Search-menu
 >> Addition of "Users of it" in the "Code Search" menu
 >> 
https://pharo.fogbugz.com/f/cases/19755/Addition-of-Users-of-it-in-the-Code-Search-menu

  Issue URL: https://pharo.fogbugz.com/f/cases/19755
  PR URL: https://github.com/pharo-project/pharo/pull/952
  Diff URL: https://github.com/pharo-project/pharo/pull/952/files

  Thanks to MarcusDenker

*  21374-Cancel-if-there-are-unsolved-depencies-during-bootstrap
 >> Metacello should fail if there are unresolved dependencies.
 >> Issue: 
https://pharo.fogbugz.com/f/cases/21374/Cancel-if-there-are-unsolved-depencies-during-bootstrap

  Issue URL: https://pharo.fogbugz.com/f/cases/21374
  PR URL: https://github.com/pharo-project/pharo/pull/918
  Diff URL: https://github.com/pharo-project/pharo/pull/918/files

  Thanks to tesonep

*  21324-Missing-Browse-receiver-feature-in-the-debugger
 >> Browser receiver command is added to debugger menu
 >> (code from pharo 6 inbox).
 >>
 >> 
https://pharo.fogbugz.com/f/cases/21324/Missing-Browse-receiver-feature-in-the-debugger

  Issue URL: https://pharo.fogbugz.com/f/cases/21324
  PR URL: https://github.com/pharo-project/pharo/pull/945
  Diff URL: https://github.com/pharo-project/pharo/pull/945/files

  Thanks to dionisiydk

*  21320-externalName-still-exists-in-class-Class
 >> externalName is removed from base Pharo classes.
 >> So it is only exists in Morphic

  Issue URL: https://pharo.fogbugz.com/f/cases/21320
  PR URL: https://github.com/pharo-project/pharo/pull/947
  Diff URL: https://github.com/pharo-project/pharo/pull/947/files

  Thanks to dionisiydk

*  20950 Ensure with a release test that super setUp/tearDown is
called in SUnit classes
 >> 
https://pharo.fogbugz.com/f/cases/20950/Ensure-with-a-release-test-that-super-setUp-is-called-in-SUnit-classes
 >>

  Issue URL: https://pharo.fogbugz.com/f/cases/20950 Ensure with a
release test that super setUp/tearDown is called in SUnit classes
  PR URL: https://github.com/pharo-project/pharo/pull/937
  Diff URL: https://github.com/pharo-project/pharo/pull/937/files

  Thanks to astares

*  21256-Deprecated-glmSubscriptions-is-used-in-GLMBrickPropertiesTrait
 >> #glmSubscriptions was deprecated for #subscriptions. Remove
its usage in GLMBrickPropertiesTrait.
 >>
 >> Case 21256 :
https://pharo.fogbugz.com/f/cases/21256/Deprecated-glmSubscriptions-is-used-in-GLMBrickPropertiesTrait

  Issue URL: https://pharo.fogbugz.com/f/cases/21256
  PR URL: https://github.com/pharo-project/pharo/pull/813
  Diff URL: https://github.com/pharo-project/pharo/pull/813/files

  Thanks to jecisc

*  21399 Use category "utilities" instead of "utils" in
GTSUnitDebuggerSmokeTest, GoferOperationTest,
MonticelloRepositoryBrowser and NativeArrayTest
 >> 
https://pharo.fogbugz.com/f/cases/21399/Use-category-utilities-instead-of-utils-in-GTSUnitDebuggerSmokeTest-GoferOperationTest-MonticelloRepositoryBrowser-and-Nat

  Issue URL: https://pharo.fogbugz.com/f/cases/21399 Use category
"utilities" instead of "utils" in GTSUnitDebuggerSmokeTest,
GoferOperationTest, MonticelloRepositoryBrowser and NativeArrayTest
  PR URL: https://github.com/pharo-project/pharo/pull/942
  Diff URL: https://github.com/pharo-project/pharo/pull/942/files

  Thanks to astares

*  21395 Remove obsolete temps in ObsoleteTest
 >> 
https://pharo.fogbugz.com/f/cases/21395/Remove-obsolete-temps-in-ObsoleteTest

  Issue URL: https://pharo.fogbugz.com/f/cases/21395 Remove
obsolete temps in ObsoleteTest
  PR URL: https://github.com/pharo-project/pharo/pull/938
  Diff URL: https://github.com/pharo-project/pharo/pull/938/files

  Thanks to astares

*  21165-Object-UI-method-should-be-packaged-in-some-UI-package
 >> Moving User interface related methods to the corresponding packages

  Issue URL: https://pharo.fogbugz.com/f/cases/21165
  PR URL: https://github.com/pharo-project/pharo/pull/949
  Diff URL: https://github.com/pharo-project/pharo/pull/949/files

  Thanks to tesonep

*  21393-reduce-QA-complaints-in-Reflectivity-tests
 >> reduce QA complaints in Reflectivity tests
 >> 
https://pharo.fogbugz.com/f/cases/21393/reduce-QA-complaints-in-Reflectivity-tests

  Issue URL: https://pharo.fogbugz.com/f/cases/21393
  PR URL: https://github.com/pharo-project/pharo/pull/935
  Diff URL: https://github.com/pharo-project/pharo/pull/935/files

  Thanks to MarcusDenker

*  21392-simplify-RFReceiverReification
 >> simplify RFReceiverReification
 >> https://pharo.fogbugz.com/f/cases/21392/simplify-RFReceiverReification

  Issue URL: https://pharo.fogbugz.com/f/cases/21392
  PR URL: https://github.com/pharo-project/pharo/pull/934
  Diff URL: 

Re: [Pharo-dev] Linux installation

[Stephane Ducasse]

Hi sean

how do we record what you did because it should not be lost.

Stef

On Fri, Feb 23, 2018 at 2:04 PM, Sean P. DeNigris  wrote:
> Steph, I agree completely. I've spent many hours documenting and researching
> ways to make Linux installation easier/better - and I don't even use Linux!
> It was only that the steady stream of questions on the MLs makes it seem
> fairly important.
>
> Sven, thanks - that's exactly what I was looking for. In my current case,
> it's just for CI because Gitlab.com doesn't support OS X targets out of the
> box, so I really have no attachment to any flavor.
>
> Norbert, that's great, thanks. I'll have to look and see how to tie a Pharo
> Docker image into the SmalltalkCI infrastructure.
>
> Finally, I notice that the following specify different sets of libs. Are
> they out of sync or for different use cases?
> -
> https://github.com/pharo-project/pharo-vm/blob/master/scripts/setup-ubuntu.sh
> - http://pharo.org/gnu-linux-installation (Ubuntu section)
>
>
>
> -
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
>

Re: [Pharo-dev] control flow graph

[Stephane Ducasse]

Clement this analysis can be done without a control flow no?


On Fri, Feb 23, 2018 at 11:47 AM, Clément Bera  wrote:
> I used that in the past on intermediate representations, I feel it is very
> useful to directly edit the code of methods with large control flows since
> when you have many closing brackets ] ] ] ] you never know where to write
> your code. Now it's specific to some use-cases such as algorithms where you
> write methods with large control flows, in most methods due to object
> oriented programming convention the control flow is not that big. In this
> context other things could be possible (Smart suggestions to move code out
> of loops, etc.)
>
>
>
>
>
>
> On Fri, Feb 23, 2018 at 11:37 AM, Stephane Ducasse 
> wrote:
>>
>> Hi
>>
>> I'm experimenting in building a control flow graph of pharo methods
>> and I would like to know if you have ideas about what we can do
>> with them to support our development environment.
>>
>> Stef
>>
>
>
>
> --
> Clément Béra
> Pharo consortium engineer
> https://clementbera.wordpress.com/
> Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq

Re: [Pharo-dev] control flow graph

[Stephane Ducasse]

Tx. I was thinking about

x = 3
  ifTrue: [^ 66]
  ifFalse: [^ 88].
^ 666

kind of analysis.
Anyway for now I just continue to do it and we will see



On Fri, Feb 23, 2018 at 2:27 PM, Peter Uhnák  wrote:
> It would be cool to have the graph for a method as a Calypso tool, so you
> can see them side by side :)
>
> On Fri, Feb 23, 2018 at 11:47 AM, Clément Bera 
> wrote:
>>
>> I used that in the past on intermediate representations, I feel it is very
>> useful to directly edit the code of methods with large control flows since
>> when you have many closing brackets ] ] ] ] you never know where to write
>> your code. Now it's specific to some use-cases such as algorithms where you
>> write methods with large control flows, in most methods due to object
>> oriented programming convention the control flow is not that big. In this
>> context other things could be possible (Smart suggestions to move code out
>> of loops, etc.)
>>
>>
>>
>>
>>
>>
>> On Fri, Feb 23, 2018 at 11:37 AM, Stephane Ducasse
>>  wrote:
>>>
>>> Hi
>>>
>>> I'm experimenting in building a control flow graph of pharo methods
>>> and I would like to know if you have ideas about what we can do
>>> with them to support our development environment.
>>>
>>> Stef
>>>
>>
>>
>>
>> --
>> Clément Béra
>> Pharo consortium engineer
>> https://clementbera.wordpress.com/
>> Bâtiment B 40, avenue Halley 59650 Villeneuve d'Ascq
>
>

Re: [Pharo-dev] [ANN] 900 pull requests closed for Pharo7!

[Stephane Ducasse]

Hi guys

this is great but there is nothing magic.
You can help reviewing submitted fixes.

Sorry to be boring but PHARO IS YOURS!!!

Stef

On Fri, Feb 23, 2018 at 1:27 PM, Marcus Denker  wrote:
> Hi,
>
> March 11, we passed 800. Today (just now) we closed 900 full requests!
>
> https://github.com/pharo-project/pharo/pulls
>
> Marcus

Re: [Pharo-dev] [update 6.0] #60535

[Stephane Ducasse]

Thanks a lot for this back port!
This is highly appreciated and yes this is taking your time and I would prefer
that you push the object centric debugger.

Stef

On Fri, Feb 23, 2018 at 4:13 PM, Marcus Denker  wrote:
> … CI just started to build:
>
> 60535
> -
>
> 21236 Sometimes the debugger opens with the context one off
> https://pharo.fogbugz.com/f/cases/21236
>
> 21324 Missing "Browse receiver" feature in the debugger
> https://pharo.fogbugz.com/f/cases/21324
>
>

Re: [Pharo-dev] #valueWithPossibleArgs:, #valueWithEnoughArguments:, and #cull:

[Stephane Ducasse]

Stephan

Can you stop ranting for ranting and be positive thinking?
Don't you think that are ARE PAYING ATTENTION!!!
We will NOT END UP looking like some other systems!

If you want to help here is a concrete proposal (we want to do it but
we are busy doing bullshit works like
reviewing fix and fixing typos around).
- Gather all the deprecated methods in the past Pharo versions
starting with Pharo 60.
- add Transform rule when posible
- package them so that people can load it and get helped during their migration

EASY NO?

sorry but I have something to hear that such kind of emails.

Stef

On Fri, Feb 23, 2018 at 8:20 PM, Stephan Eggermont  wrote:
> Sean P. DeNigris  wrote:
>> Or are you saying there should be a collection of rewrite rules even after
>> the method is totally removed so one can bring a very old project up to the
>> newest APIs?
>
> Making sure the code works in each intermediate version of Pharo is
> increasingly unattractive. It also requires indefinite support of all the
> old pharo versions. A collection of separate rewrite rules looks to me like
> the right thing to both explain changes and speed up migrations.
>
> Stephan
>
>