September 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] review pull request changes view

by Esteban Lorenzano

> On 1 Sep 2017, at 16:02, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > >> On 1 Sep 2017, at 15:50, Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>> wrote: >> >> >> >> 2017-09-01 15:03 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: >> >>> On 1 Sep 2017, at 14:51, Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>> wrote: >>> >>> >>> >>> 2017-09-01 14:48 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>>: >>> When reviewing a pull request, I see this in the changes view: >>> The tab title says >>> "left working copy / right incoming update" >>> but the code on the right side is what is current in my image >>> >>> <grafik.png> >>> >>> >>> And I don't think "working copy" is the correct naming, as this view lets me diff changes within >>> that history, so it may be that none of this code is actually in my "working copy", no ? >>> >>> >>> BTW, this is extremly unstable, reviewing a pull request, crashes a lot (the vm) >> >> on windows? >> >>> >> >> >> Yes, >> >> attached a another crash.dmp (maybe it helps) >> >> <crash.dmp> > > can you tell me the PR you were analysing ? ah, and btwâ¦ can you update with latest dev-0.5? I made some changes that may help there that I still do not merge into master. Esteban > > Esteban

Sept. 1, 2017

Re: [Pharo-dev] review pull request changes view

by Esteban Lorenzano

> On 1 Sep 2017, at 15:50, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2017-09-01 15:03 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > >> On 1 Sep 2017, at 14:51, Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>> wrote: >> >> >> >> 2017-09-01 14:48 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>>: >> When reviewing a pull request, I see this in the changes view: >> The tab title says >> "left working copy / right incoming update" >> but the code on the right side is what is current in my image >> >> <grafik.png> >> >> >> And I don't think "working copy" is the correct naming, as this view lets me diff changes within >> that history, so it may be that none of this code is actually in my "working copy", no ? >> >> >> BTW, this is extremly unstable, reviewing a pull request, crashes a lot (the vm) > > on windows? > >> > > > Yes, > > attached a another crash.dmp (maybe it helps) > > <crash.dmp> can you tell me the PR you were analysing ? Esteban

Sept. 1, 2017

Re: [Pharo-dev] review pull request changes view

by Nicolai Hess

2017-09-01 15:03 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > On 1 Sep 2017, at 14:51, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2017-09-01 14:48 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> When reviewing a pull request, I see this in the changes view: >> The tab title says >> "left working copy / right incoming update" >> but the code on the right side is what is current in my image >> >> <grafik.png> >> >> >> And I don't think "working copy" is the correct naming, as this view lets >> me diff changes within >> that history, so it may be that none of this code is actually in my >> "working copy", no ? >> > > > BTW, this is extremly unstable, reviewing a pull request, crashes a lot > (the vm) > > > on windows? > > > > Yes, attached a another crash.dmp (maybe it helps)

Sept. 1, 2017

1st CfP: OOPS @ SAC 2018 - April 9 - 13, Pau, France

by Nick Papoylias

************************************************** OOPS 2018 Call for Papers Object-Oriented Programming Languages and Systems http://oops.disi.unige.it/OOPS18 ************************************************** Technical Track at the 33rd ACM Symposium on Applied Computing, SAC 2018 https://www.sigapp.org/sac/sac2018/index.html April 9 - 13, 2018 Pau, France - Important Dates Submission of regular papers and SRC abstracts September 15, 2017 Paper and SRC notifications November 10, 2017 Paper and SRC camera-ready copies November 25, 2017 Author registration December 10, 2017 SAC 2018 April 9 - 13, 2018 - Track Chair Davide Ancona (davide.ancona(a)unige.it) DIBRIS, University of Genova, Italy - SAC 2018 For the past thirty two years, the ACM Symposium on Applied Computing (SAC) has been a primary gathering forum for applied computer scientists, computer engineers, software engineers, and application developers from around the world. SAC 2018 is sponsored by the ACM Special Interest Group on Applied Computing (SIGAPP) and is hosted by hosted by UniversitÃ© de Pau et des Pays de l'Adour (UPPA), Pau, France. - Call For Student Research Abstracts Graduate students seeking feedback from the scientific community on their research ideas are invited to submit original abstracts of their research work in areas of experimental computing and application development related to SAC 2018 Tracks. The Student Research Competition (SRC) Program is designed to provide graduate students the opportunity to meet and exchange ideas with researchers and practitioners in their areas of interest. - OOPS Track: Aims and Topics Object-oriented programming (OOP) has become the mainstream programming paradigm for developing complex software systems in most application domains. However, existing OO languages and platforms need to evolve to meet the continuous demand for new abstractions, features, and tools able to reduce the time, effort, and cost of creating object-oriented software systems, and improving their performance, quality and usability. To this aim, OOPS is seeking for research advances bringing benefits in all those typical aspects of software development, such as modeling, prototyping, design, implementation, concurrency and distribution, code generation, analysis, verification, testing, debugging, evaluation, deployment, maintenance, reuse, and software evolution and adaptation. The specific topics of interest for the OOPS track include, but are not limited to, the following: * Aspects and components * Code generation, and optimization, just-in-time compilation * Context-oriented programming * Databases and persistence * Distribution and concurrency * Dynamic and scripting languages * Evaluation * Feature Oriented Software Development and Programming * Formal verification * Internet of Things technology and programming * Integration with other paradigms * Interoperability, versioning and software evolution and adaptation * Language design and implementation * Modular and generic programming * Reflection, meta-programming * Runtime verification and monitoring * Safe, secure and dependable software * Static analysis * Testing and debugging * Type systems and type inference * Virtual machines OOPS offers a great opportunity to the OOP community to gain visibility, and to exploit the inter-disciplinary nature of SAC. - Submission Instructions Prospective papers should be submitted to the track in pdf format using the START submission system for regular and SRC papers available through the SAC 2018 home page. Submission of the same paper to multiple tracks is not allowed; all papers should represent original and previously unpublished works that are currently not under review in any conference or journal. Both basic and applied research papers are welcome. SAC 2018 will use double-blind reviewing; to facilitate this, author name(s) and institution(s) must be omitted, and references to authors' own related work should be in the third person. The format of the paper must adhere to the sig-alternate style (http://www.acm.org/sigs/publications/proceedings-templates) Full papers are limited to 8 pages, in camera-ready format, included in the registration fee. Authors have the option to include up to two (2) extra pages at additional fee of US$80 per page. Papers accepted as posters are limited to 3 pages, in camera-ready format, included in the registration fee. Authors have the option to include only one (1) extra page at additional fee of US$80. SRC abstracts are limited to 2 pages, in camera-ready format, included in the registration fee. No extra pages are allowed. Papers that fall short the above requirements are subjected to rejection. All papers must be submitted by September 15, 2017. For more information please visit the SAC 2018 home page. - Proceedings Accepted papers will be published by ACM in the annual conference proceedings. Accepted posters will be published as extended abstracts in the same proceedings. Paper registration is required, allowing the inclusion of the papers and posters in the conference proceedings. An author or a proxy attending SAC MUST present the paper. This is a requirement for all accepted papers, posters, and invited SRC submissions to be included in the ACM digital library. No-show of scheduled papers, posters, and student research abstracts will result in excluding them from the ACM digital library. Student registration is only intended to encourage student attendance and does not cover inclusion of papers/posters in the conference proceedings. Finally, following the tradition of the past OOPS editions (http://oops.disi.unige.it/special-issues) depending on the quality and the overall number of accepted papers, authors of selected papers will be invited to submit an extended version for a journal special issue ( http://oops.disi.unige.it/special-issues) after the conference.

Sept. 1, 2017

Re: [Pharo-dev] review pull request changes view

by Esteban Lorenzano

> On 1 Sep 2017, at 14:51, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2017-09-01 14:48 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>>: > When reviewing a pull request, I see this in the changes view: > The tab title says > "left working copy / right incoming update" > but the code on the right side is what is current in my image > > <grafik.png> > > > And I don't think "working copy" is the correct naming, as this view lets me diff changes within > that history, so it may be that none of this code is actually in my "working copy", no ? > > > BTW, this is extremly unstable, reviewing a pull request, crashes a lot (the vm) on windows? >

Sept. 1, 2017

Re: [Pharo-dev] review pull request changes view

by Nicolai Hess

2017-09-01 14:48 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: > When reviewing a pull request, I see this in the changes view: > The tab title says > "left working copy / right incoming update" > but the code on the right side is what is current in my image > > [image: Inline-Bild 1] > > > And I don't think "working copy" is the correct naming, as this view lets > me diff changes within > that history, so it may be that none of this code is actually in my > "working copy", no ? > BTW, this is extremly unstable, reviewing a pull request, crashes a lot (the vm)

Sept. 1, 2017

review pull request changes view

by Nicolai Hess

When reviewing a pull request, I see this in the changes view: The tab title says "left working copy / right incoming update" but the code on the right side is what is current in my image [image: Inline-Bild 1] And I don't think "working copy" is the correct naming, as this view lets me diff changes within that history, so it may be that none of this code is actually in my "working copy", no ?

Sept. 1, 2017

Re: [Pharo-dev] BOF at ESUG - How about a BOF on Gemstone development environments?

by Tim Mackinnon

I'm envious as I couldn't make it to Esug - but I'd love to hear any conclusions/insights from that bof. Iceberg/git is such a transformative step that we need all the knowledge spread we can get. Tim Sent from my iPhone > On 1 Sep 2017, at 12:40, Reg Krock via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > <mime-attachment>

Sept. 1, 2017

BOF at ESUG - How about a BOF on Gemstone development environments?

by Reg Krock

> On 1 Sep2017, at 6:35 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > I would also be interested in a Pillar BOF. > > Doru > > >> On Sep 1, 2017, at 11:43 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> May be wednesday afternoon the talks >> >> On Fri, Sep 1, 2017 at 9:17 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> +1 >>> >>> Doru >>> >>> >>>> On Sep 1, 2017, at 8:58 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>> +1 :) >>>> >>>>> On 31 Aug 2017, at 20:11, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>>>> >>>>> Hi >>>>> >>>>> I'm wondering if we should not do a BOF around Pharo iceberg at ESUG. >>>>> >>>>> Stef >>>>> >>>> >>>> >>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> âLive like you mean it." >>> >>> >> > > -- > www.tudorgirba.com > www.feenk.com > > "We are all great at making mistakes." > > > > > > > > >

Sept. 1, 2017

Re: [Pharo-dev] Pharo / Iceberg BOF at ESUG

by Tudor Girba

Hi, I would also be interested in a Pillar BOF. Doru > On Sep 1, 2017, at 11:43 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > May be wednesday afternoon the talks > > On Fri, Sep 1, 2017 at 9:17 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> +1 >> >> Doru >> >> >>> On Sep 1, 2017, at 8:58 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> +1 :) >>> >>>> On 31 Aug 2017, at 20:11, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>>> >>>> Hi >>>> >>>> I'm wondering if we should not do a BOF around Pharo iceberg at ESUG. >>>> >>>> Stef >>>> >>> >>> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> âLive like you mean it." >> >> > -- www.tudorgirba.com www.feenk.com "We are all great at making mistakes."

Sept. 1, 2017