November 2019 - Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #975: Completion: More Cleanups

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #975 was: FAILURE. The Pull Request #5143 was integrated: "Completion: More Cleanups" Pull request url: https://github.com/pharo-project/pharo/pull/5143 Issue Url: https://github.com/pharo-project/pharo/issues/CompletionCleanUps Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 15, 2019

[Pharo 8.0] Build #974: Revert "Rules-are-failing-on-bytearrays"

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #974 was: SUCCESS. The Pull Request #5144 was integrated: "Revert "Rules-are-failing-on-bytearrays"" Pull request url: https://github.com/pharo-project/pharo/pull/5144 Issue Url: https://github.com/pharo-project/pharo/issues/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 15, 2019

[Pharo 8.0] Build #973: Completion: #completionEntries creates entries

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #973 was: SUCCESS. The Pull Request #5135 was integrated: "Completion: #completionEntries creates entries" Pull request url: https://github.com/pharo-project/pharo/pull/5135 Issue Url: https://github.com/pharo-project/pharo/issues/Completion Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 15, 2019

[Pharo 8.0] Build #972: 4967-Base-image-contains-invalid-source-pointers

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #972 was: FAILURE. The Pull Request #5120 was integrated: "4967-Base-image-contains-invalid-source-pointers" Pull request url: https://github.com/pharo-project/pharo/pull/5120 Issue Url: https://github.com/pharo-project/pharo/issues/4967 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 15, 2019

Re: [Pharo-dev] two issues: GC and wrong pointers

by Juraj Kubelka

Hi, we found a script that reproduces the GC segmentation fault. The report is here - https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/444 <https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/444> - which is likely the same issue as reported here: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391 <https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391> Best, Juraj > On 12 Nov 2019, at 12:40, ducasse <stepharo(a)netcourrier.com> wrote: > > ok > It may be related to the bug pablo is working on. > So it would be good to see how many times the image is saved. > > Stef > >> On 12 Nov 2019, at 08:58, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >> >> ith all other bug reports. >

Nov. 13, 2019

MoreVMs 2020 : Workshop on Modern Language Runtimes, Ecosystems, and VMs

by Fabio Niephaus

============================================================================ Call for Extended Abstracts and Talks: MoreVMsâ20 4th Workshop on Modern Language Runtimes, Ecosystems, and VMs Co-located with â¹Programmingâºâ20 March 23rd or 24th, 2020, Porto, Portugal https://2020.programming-conference.org/home/MoreVMs-2020 ============================================================================ Following three previous successful editions, the MoreVMsâ20 workshop aims to bring together industrial and academic programmers to discuss the design, implementation, and usage of modern languages and runtimes. This includes aspects such as reuse of language runtimes, modular implementation, language design, and compilation strategies. By bringing together both researchers and practitioners, the workshop aims to enable a diverse discussion on how languages and runtimes are currently being utilized, and where they need to improve further. In addition to conventional workshop-style submissions, MoreVMs also accepts (and encourages) submissions that present early-stage work and emerging ideas. Relevant topics include, but are definitely not limited to, the following: - Extensible VM design (compiler- or interpreter-based VMs) - Reusable components (e.g. interpreters, garbage collectors, ...) - Static and dynamic compilation techniques - Techniques for targeting high-level languages such as JavaScript - Interoperability between languages - Tooling support (e.g. debugging, profiling, etc.) - Programming language development environments - Case studies of existing language implementation approaches - Language implementation challenges and trade-offs - Surveys and usage reports to understand usage in the wild - Ideas for more predictable performance - Ideas for how VMs could take advantage of new hardware features - Ideas for how we should build languages in the future Workshop Format and Submissions ------------------------------- We welcome presentation proposals in the form of extended abstracts (2 to 4 pages long) and talk proposals (title and 400 words abstract) discussing new techniques, insights, experiences, works-in-progress, as well as future visions, from either an academic or industrial perspective. The extended abstracts and talk proposals, and if the speakers wish, their slides, will be published on the workshop's website. Alternatively, extended abstracts can be published as part of the companion of â¹Programmingâºâ20 in the ACM DL. Publication in the ACM DL is conditional on the acceptance by the program committee. Please note that MoreVMsâ20 is organized as an academic workshop, and as such, speakers will be required to register for the workshop. We regret that we are unable to cover registration, travel, or accommodation costs for authors. Author Instructions ------------------- Submissions should use the ACM `acmart` format: https://www.acm.org/publications/proceedings-template If you are using LaTeX, submissions should use the 'acmart' document class with the 'sigconf' option, and with a font size of 9 point. Please use the Libertine/Biolinum font family. Please include page numbers in your submission using the LaTeX command `\settopmatter{printfolios=true}`. All submissions should be in PDF format. Please also ensure that your submission is legible when printed on a black and white printer. In particular, please check that colors remain distinct and font sizes are legible. Submission Site: https://easychair.org/conferences/?conf=morevms20 Important Dates --------------- Extended abstract and talk submissions: 2020-01-10 Author notification: 2020-02-10 Camera Ready: 2020-02-21 Workshop: 2020-03-23 or 2020-03-24 All deadlines are Anywhere on Earth (AoE), i.e. GMT/UTC-12:00 hour. Invited Speakers ----------------- Roman Kennke, Shenandoah GC Project Lead, Red Hat Leszek Swirski, Software Engineer, V8 Team, Google Program Committee ----------------- Nicolas B. Pierron, Mozilla, France ClÃ©ment BÃ©ra, Google, Denmark Elisa Gonzalez Boix, Vrije Universiteit Brussel, Belgium Stephen Kell, University of Kent, United Kingdom Christoph Kirsch, University of Salzburg, Austria Hidehiko Masuhara, Tokyo Institute of Technology, Japan Gabriela Alexandra Moldovan, Cloudflare, United Kingdom David Pearce, Victoria University of Wellington, New Zealand Manuel Rigger, ETH Zurich, Switzerland Jennifer B. Sartor, Ghent University and Vrije Universiteit Brussel, Belgium Tomoharu Ugawa, Kochi University of Technology, Japan Michael Van De Vanter, Cal Poly, San Luis Obispo, United States Andy Wingo, Igalia, S.L., United States Organizers ---------- Edd Barrett, King's College London, United Kingdom Fabio Niephaus, Hasso Plattner Institute, University of Potsdam, Germany

Nov. 13, 2019

Re: [Pharo-dev] deprecating use traditional formatter

by ducasse

So I did it in https://github.com/Ducasse/enlumineur I will work on the removal of the previous formatter and the introduction of the new one. Stef > On 13 Nov 2019, at 10:06, ducasse <stepharo(a)netcourrier.com> wrote: > > I will do it :) > >> On 13 Nov 2019, at 10:05, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >> >> >>> On 13 Nov 2019, at 09:04, ducasse <stepharo(a)netcourrier.com <mailto:stepharo@netcourrier.com>> wrote: >>> >>> Hi >>> >>> In the new implementation of the code formattter I will remove useTraditionalPrecedence. >>> This settings put additional parentheses around binary selector but I find it cumbersome >>> >>> While it may make sense for >>> >>> it turns >>> foo >>> ^ 1 + 2 * 3 >>> >>> into >>> >>> foo >>> ^ (1 + 2) * 3 >>> >>> foo >>> ^ 1 * 3 + 2 >>> >>> foo >>> ^ (1 | 2) % 3 >>> >>> foo >>> >>> ^ 1 % 2 | 3 >>> >>> So let me know what you think but I will be hard to convince :) >>> >> I vote to remove it. >> >> The RB AST encodes parenthesis information, so that means that we can have >> a pretty printer keeping the parenthesis if they have been added by the original author. >> >> Adding new ones makes no sense to me. >> >> So I vote to remove. >> >> Marcus >

Nov. 13, 2019

Re: [Pharo-dev] deprecating use traditional formatter

by ducasse

I will do it :) > On 13 Nov 2019, at 10:05, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 13 Nov 2019, at 09:04, ducasse <stepharo(a)netcourrier.com> wrote: >> >> Hi >> >> In the new implementation of the code formattter I will remove useTraditionalPrecedence. >> This settings put additional parentheses around binary selector but I find it cumbersome >> >> While it may make sense for >> >> it turns >> foo >> ^ 1 + 2 * 3 >> >> into >> >> foo >> ^ (1 + 2) * 3 >> >> foo >> ^ 1 * 3 + 2 >> >> foo >> ^ (1 | 2) % 3 >> >> foo >> >> ^ 1 % 2 | 3 >> >> So let me know what you think but I will be hard to convince :) >> > I vote to remove it. > > The RB AST encodes parenthesis information, so that means that we can have > a pretty printer keeping the parenthesis if they have been added by the original author. > > Adding new ones makes no sense to me. > > So I vote to remove. > > Marcus

Nov. 13, 2019

Re: [Pharo-dev] deprecating use traditional formatter

by Marcus Denker

> On 13 Nov 2019, at 09:04, ducasse <stepharo(a)netcourrier.com> wrote: > > Hi > > In the new implementation of the code formattter I will remove useTraditionalPrecedence. > This settings put additional parentheses around binary selector but I find it cumbersome > > While it may make sense for > > it turns > foo > ^ 1 + 2 * 3 > > into > > foo > ^ (1 + 2) * 3 > > foo > ^ 1 * 3 + 2 > > foo > ^ (1 | 2) % 3 > > foo > > ^ 1 % 2 | 3 > > So let me know what you think but I will be hard to convince :) > I vote to remove it. The RB AST encodes parenthesis information, so that means that we can have a pretty printer keeping the parenthesis if they have been added by the original author. Adding new ones makes no sense to me. So I vote to remove. Marcus

Nov. 13, 2019

deprecating use traditional formatter

by ducasse

Hi In the new implementation of the code formattter I will remove useTraditionalPrecedence. This settings put additional parentheses around binary selector but I find it cumbersome While it may make sense for it turns foo ^ 1 + 2 * 3 into foo ^ (1 + 2) * 3 foo ^ 1 * 3 + 2 foo ^ (1 | 2) % 3 foo ^ 1 % 2 | 3 So let me know what you think but I will be hard to convince :) Stef

Nov. 13, 2019

[Pharo 8.0] Build #971: CompletionEntryRemoveContextParameter

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #971 was: FAILURE. The Pull Request #5123 was integrated: "CompletionEntryRemoveContextParameter" Pull request url: https://github.com/pharo-project/pharo/pull/5123 Issue Url: https://github.com/pharo-project/pharo/issues/CompletionEntryRemoveContextP… Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 13, 2019

Re: [Pharo-dev] two issues: GC and wrong pointers

by ducasse

ok It may be related to the bug pablo is working on. So it would be good to see how many times the image is saved. Stef > On 12 Nov 2019, at 08:58, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > ith all other bug reports.

Nov. 12, 2019

Re: [Pharo-dev] [ANN] Pharo Consortium New Academic Member: UniversitÃ© de Maroua

by Santiago Bragagnolo

Great! El mar., 12 de nov. de 2019 10:09, Marcus Denker <marcus.denker(a)inria.fr> escribiÃ³: > The Pharo Consortium is very happy to announce that the UniversitÃ© de > Maroua has joined the Consortium as an Academic Member. > > About > - UniversitÃ© de Maroua: http://www.univ-maroua.cm/ > - Pharo Consortium: http://consortium.pharo.org > > The goal of the Pharo Consortium is to allow companies and institutions to > support the ongoing development and future of Pharo. > > Individuals can support Pharo via the Pharo Association: > > - http://association.pharo.org >

Nov. 12, 2019

[ANN] Pharo Consortium New Academic Member: UniversitÃ© de Maroua

by Marcus Denker

The Pharo Consortium is very happy to announce that the UniversitÃ© de Maroua has joined the Consortium as an Academic Member. About - UniversitÃ© de Maroua: http://www.univ-maroua.cm/ - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: - http://association.pharo.org

Nov. 12, 2019

Re: [Pharo-dev] two issues: GC and wrong pointers

by Tudor Girba

Hi, Yes, I know itâs not a good public bug report. That is why I asked for help. The problem is that this is not easily reproducible outside of specific cases. We encountered it in the context of GT which has double the code as compared to Pharo. So, to test it outside of GT, for the last couple of weeks we manipulated some data in plain Pharo, and we still got to the problem a couple of times (though it appears less often). We do not know yet how to reproduce it with anonymous data. That is why I said that some pairing might help. In parallel we are trying to reproduce it, like we do with all other bug reports. Cheers, Doru > On Nov 12, 2019, at 8:00 AM, ducasse <stepharo(a)netcourrier.com> wrote: > > > >> On 11 Nov 2019, at 12:57, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> During our work we encountered two issues we think should be considered critical. >> >> The first is that the garbage collector is unreliable on larger images: >> https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391 >> We stumble on this when we manipulate larger pieces of data quite consistently in plain Pharo (7 or 8). We lack the knowledge of how to approach it, but we would happily pair and try to reproduce it with someone. > > > Doru > > To me this is not really a good bug report. > How can we reproduce it? > What is a big image? > > The first thing to do is to get a simple reproducible case. > This is what pavel did with the crash on normal images. > Can you see if you can do something like that? > It will help us trying to fix it. > > S. > > > -- feenk.com "What is more important: To be happy, or to make happy?"

Nov. 12, 2019

Re: [Pharo-dev] two issues: GC and wrong pointers

by ducasse

> On 11 Nov 2019, at 12:57, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > During our work we encountered two issues we think should be considered critical. > > The first is that the garbage collector is unreliable on larger images: > https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391 > We stumble on this when we manipulate larger pieces of data quite consistently in plain Pharo (7 or 8). We lack the knowledge of how to approach it, but we would happily pair and try to reproduce it with someone. Doru To me this is not really a good bug report. How can we reproduce it? What is a big image? The first thing to do is to get a simple reproducible case. This is what pavel did with the crash on normal images. Can you see if you can do something like that? It will help us trying to fix it. S.

Nov. 12, 2019

Re: [Pharo-dev] make github issues clearer?

by Myroslava Romaniuk

hi Stef On Mon, 4 Nov 2019 at 11:16, ducasse <stepharo(a)netcourrier.com> wrote: > Yes sometimes describing it takes more time than fixing it. > if that is the case, then maybe you should just fix it. easy issues are cool in theory but if they are not sufficiently explained they will not be of any use to beginner devs who want to contribute, either. if you are creating an easy issue and marking it 'beginner', the description should be level-appropriate. and in general there are templates that make this whole process easier/faster because you have some things pre-filled and you have section descriptions that helps you quickly remember the things you need to describe. my whole point was about optimising this process on the org level: individual contribution certainly counts for something, but there's no need to reinvent the wheel. best, Myroslava

Nov. 11, 2019

Re: [Pharo-dev] two issues: GC and wrong pointers

by Tudor Girba

Thanks Marcus! Alistair reviewed the issue (https://github.com/pharo-project/pharo/pull/5120) and the pull request looks great. Cool work :). Cheers, Doru > On Nov 11, 2019, at 3:51 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 11 Nov 2019, at 15:04, ducasse <stepharo(a)netcourrier.com> wrote: >> >> marcus I read your fix and I do not understand why the previous way was a problem. >> What was your hypothesis? >> > > I think the problem is that it forces recompiling methods while already loading code, which leads to some strange effect.. that I think > the MethodChanged that monticello does at the end references the old method, but that got recompiled in the meantime. > > Something like that. > >> Stef >> >>> On 11 Nov 2019, at 14:46, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> >>>>>> >>>>>> Hi, >>>>>> >>>>>> During our work we encountered two issues we think should be considered critical. >>>>>> >>>>>> The first is that the garbage collector is unreliable on larger images: >>>>>> https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391 >>>>>> We stumble on this when we manipulate larger pieces of data quite consistently in plain Pharo (7 or 8). We lack the knowledge of how to approach it, but we would happily pair and try to reproduce it with someone. >>>>>> >>>>>> The second one is that the sources contain wrong pointers, and this makes it hard to work with TFFI: >>>>>> https://github.com/pharo-project/pharo/issues/4967 >>>>>> This is already marked as important. We spent quite some time investigating this, especially in the context of TFFI, and we would be happy to pair to work through it. >>>>>> >>> >>> I think my PR fixes itâ¦ the PR is green and the downloaded artefact seems to not show any problematic methods anymore: >>> >>> https://github.com/pharo-project/pharo/pull/5120 >>> >>> >>> >>> Marcus >> > -- feenk.com "To utilize feedback, you first have to acquire it."

Nov. 11, 2019

Re: [Pharo-dev] two issues: GC and wrong pointers

by Marcus Denker

> On 11 Nov 2019, at 15:04, ducasse <stepharo(a)netcourrier.com> wrote: > > marcus I read your fix and I do not understand why the previous way was a problem. > What was your hypothesis? > I think the problem is that it forces recompiling methods while already loading code, which leads to some strange effect.. that I think the MethodChanged that monticello does at the end references the old method, but that got recompiled in the meantime. Something like that. > Stef > >> On 11 Nov 2019, at 14:46, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >> >>>>> >>>>> Hi, >>>>> >>>>> During our work we encountered two issues we think should be considered critical. >>>>> >>>>> The first is that the garbage collector is unreliable on larger images: >>>>> https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391 <https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391> >>>>> We stumble on this when we manipulate larger pieces of data quite consistently in plain Pharo (7 or 8). We lack the knowledge of how to approach it, but we would happily pair and try to reproduce it with someone. >>>>> >>>>> The second one is that the sources contain wrong pointers, and this makes it hard to work with TFFI: >>>>> https://github.com/pharo-project/pharo/issues/4967 <https://github.com/pharo-project/pharo/issues/4967> >>>>> This is already marked as important. We spent quite some time investigating this, especially in the context of TFFI, and we would be happy to pair to work through it. >>>>> >> >> I think my PR fixes itâ¦ the PR is green and the downloaded artefact seems to not show any problematic methods anymore: >> >> https://github.com/pharo-project/pharo/pull/5120 <https://github.com/pharo-project/pharo/pull/5120> >> >> >> >> Marcus >

Nov. 11, 2019

Re: [Pharo-dev] two issues: GC and wrong pointers

by ducasse

marcus I read your fix and I do not understand why the previous way was a problem. What was your hypothesis? Stef > On 11 Nov 2019, at 14:46, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >>>> >>>> Hi, >>>> >>>> During our work we encountered two issues we think should be considered critical. >>>> >>>> The first is that the garbage collector is unreliable on larger images: >>>> https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391 <https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391> >>>> We stumble on this when we manipulate larger pieces of data quite consistently in plain Pharo (7 or 8). We lack the knowledge of how to approach it, but we would happily pair and try to reproduce it with someone. >>>> >>>> The second one is that the sources contain wrong pointers, and this makes it hard to work with TFFI: >>>> https://github.com/pharo-project/pharo/issues/4967 >>>> This is already marked as important. We spent quite some time investigating this, especially in the context of TFFI, and we would be happy to pair to work through it. >>>> > > I think my PR fixes itâ¦ the PR is green and the downloaded artefact seems to not show any problematic methods anymore: > > https://github.com/pharo-project/pharo/pull/5120 <https://github.com/pharo-project/pharo/pull/5120> > > > > Marcus

Nov. 11, 2019

Re: [Pharo-dev] two issues: GC and wrong pointers

by ducasse

May be we have two problems then :( Because we have problem without a large image. Stef > On 11 Nov 2019, at 14:44, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > For the GC problem from https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391, there is no threading involved. Just invoking full GC in a large image. > > Cheers, > Doru > > > >> On Nov 11, 2019, at 1:47 PM, ducasse <stepharo(a)netcourrier.com> wrote: >> >> Hi doru >> >> >> Can you tell us more? How many threads are running? how many times did you save the image? >> Pablo is investigating a bug related to the GC that happens when we have many threads and saved the image >> multiple times. He was on it since a couple of days. >> >> Now Pablo is attending Smalltalks and will be on vacation until end of the month. >> Guille is on father leave and coming back to work one day a week. >> >> So we are concerned about this problem but we cannot really allocate people on it before beginning of december. >> >> S. >> >>> On 11 Nov 2019, at 12:57, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> Hi, >>> >>> During our work we encountered two issues we think should be considered critical. >>> >>> The first is that the garbage collector is unreliable on larger images: >>> https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391 >>> We stumble on this when we manipulate larger pieces of data quite consistently in plain Pharo (7 or 8). We lack the knowledge of how to approach it, but we would happily pair and try to reproduce it with someone. >>> >>> The second one is that the sources contain wrong pointers, and this makes it hard to work with TFFI: >>> https://github.com/pharo-project/pharo/issues/4967 >>> This is already marked as important. We spent quite some time investigating this, especially in the context of TFFI, and we would be happy to pair to work through it. >>> >>> Would anyone be available for a collaboration in the following days? >>> >>> Cheers, >>> Doru >>> >>> >>> -- >>> feenk.com >>> >>> "Not knowing how to do something is not an argument for how it cannot be done." >>> >>> >> >> >> > > -- > feenk.com > > "Value is always contextual." > > > > > > >

Nov. 11, 2019

Re: [Pharo-dev] two issues: GC and wrong pointers

by Marcus Denker

>>> >>> Hi, >>> >>> During our work we encountered two issues we think should be considered critical. >>> >>> The first is that the garbage collector is unreliable on larger images: >>> https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391 >>> We stumble on this when we manipulate larger pieces of data quite consistently in plain Pharo (7 or 8). We lack the knowledge of how to approach it, but we would happily pair and try to reproduce it with someone. >>> >>> The second one is that the sources contain wrong pointers, and this makes it hard to work with TFFI: >>> https://github.com/pharo-project/pharo/issues/4967 >>> This is already marked as important. We spent quite some time investigating this, especially in the context of TFFI, and we would be happy to pair to work through it. >>> I think my PR fixes itâ¦ the PR is green and the downloaded artefact seems to not show any problematic methods anymore: https://github.com/pharo-project/pharo/pull/5120 <https://github.com/pharo-project/pharo/pull/5120> Marcus

Nov. 11, 2019

Re: [Pharo-dev] two issues: GC and wrong pointers

by Tudor Girba

Hi, For the GC problem from https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391, there is no threading involved. Just invoking full GC in a large image. Cheers, Doru > On Nov 11, 2019, at 1:47 PM, ducasse <stepharo(a)netcourrier.com> wrote: > > Hi doru > > > Can you tell us more? How many threads are running? how many times did you save the image? > Pablo is investigating a bug related to the GC that happens when we have many threads and saved the image > multiple times. He was on it since a couple of days. > > Now Pablo is attending Smalltalks and will be on vacation until end of the month. > Guille is on father leave and coming back to work one day a week. > > So we are concerned about this problem but we cannot really allocate people on it before beginning of december. > > S. > >> On 11 Nov 2019, at 12:57, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> During our work we encountered two issues we think should be considered critical. >> >> The first is that the garbage collector is unreliable on larger images: >> https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391 >> We stumble on this when we manipulate larger pieces of data quite consistently in plain Pharo (7 or 8). We lack the knowledge of how to approach it, but we would happily pair and try to reproduce it with someone. >> >> The second one is that the sources contain wrong pointers, and this makes it hard to work with TFFI: >> https://github.com/pharo-project/pharo/issues/4967 >> This is already marked as important. We spent quite some time investigating this, especially in the context of TFFI, and we would be happy to pair to work through it. >> >> Would anyone be available for a collaboration in the following days? >> >> Cheers, >> Doru >> >> >> -- >> feenk.com >> >> "Not knowing how to do something is not an argument for how it cannot be done." >> >> > > > -- feenk.com "Value is always contextual."

Nov. 11, 2019

[Pharo 8.0] Build #970: bind on collections

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #970 was: FAILURE. The Pull Request #5108 was integrated: "bind on collections" Pull request url: https://github.com/pharo-project/pharo/pull/5108 Issue Url: https://github.com/pharo-project/pharo/issues/collectoinBind Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 11, 2019

[Pharo 8.0] Build #969: 4337-tests-of-RB-should-not-use-category-based-class-definition-but-package

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #969 was: FAILURE. The Pull Request #5106 was integrated: "4337-tests-of-RB-should-not-use-category-based-class-definition-but-package" Pull request url: https://github.com/pharo-project/pharo/pull/5106 Issue Url: https://github.com/pharo-project/pharo/issues/4337 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 11, 2019

Re: [Pharo-dev] two issues: GC and wrong pointers

by ducasse

Hi doru Can you tell us more? How many threads are running? how many times did you save the image? Pablo is investigating a bug related to the GC that happens when we have many threads and saved the image multiple times. He was on it since a couple of days. Now Pablo is attending Smalltalks and will be on vacation until end of the month. Guille is on father leave and coming back to work one day a week. So we are concerned about this problem but we cannot really allocate people on it before beginning of december. S. > On 11 Nov 2019, at 12:57, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > During our work we encountered two issues we think should be considered critical. > > The first is that the garbage collector is unreliable on larger images: > https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391 > We stumble on this when we manipulate larger pieces of data quite consistently in plain Pharo (7 or 8). We lack the knowledge of how to approach it, but we would happily pair and try to reproduce it with someone. > > The second one is that the sources contain wrong pointers, and this makes it hard to work with TFFI: > https://github.com/pharo-project/pharo/issues/4967 > This is already marked as important. We spent quite some time investigating this, especially in the context of TFFI, and we would be happy to pair to work through it. > > Would anyone be available for a collaboration in the following days? > > Cheers, > Doru > > > -- > feenk.com > > "Not knowing how to do something is not an argument for how it cannot be done." > >

Nov. 11, 2019

Re: [Pharo-dev] two issues: GC and wrong pointers

by Marcus Denker

> On 11 Nov 2019, at 12:57, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > During our work we encountered two issues we think should be considered critical. > > The first is that the garbage collector is unreliable on larger images: > https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391 > We stumble on this when we manipulate larger pieces of data quite consistently in plain Pharo (7 or 8). We lack the knowledge of how to approach it, but we would happily pair and try to reproduce it with someone. > > The second one is that the sources contain wrong pointers, and this makes it hard to work with TFFI: > https://github.com/pharo-project/pharo/issues/4967 > This is already marked as important. We spent quite some time investigating this, especially in the context of TFFI, and we would be happy to pair to work through it. > This one I want to have a look atâ¦ I think the solution is to remove the magic and maybe even think about integrating the FFI plugin into the compiler. I am available Tuesday afternoon. Marcus

Nov. 11, 2019

two issues: GC and wrong pointers

by Tudor Girba

Hi, During our work we encountered two issues we think should be considered critical. The first is that the garbage collector is unreliable on larger images: https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/391 We stumble on this when we manipulate larger pieces of data quite consistently in plain Pharo (7 or 8). We lack the knowledge of how to approach it, but we would happily pair and try to reproduce it with someone. The second one is that the sources contain wrong pointers, and this makes it hard to work with TFFI: https://github.com/pharo-project/pharo/issues/4967 This is already marked as important. We spent quite some time investigating this, especially in the context of TFFI, and we would be happy to pair to work through it. Would anyone be available for a collaboration in the following days? Cheers, Doru -- feenk.com "Not knowing how to do something is not an argument for how it cannot be done."

Nov. 11, 2019

[Pharo 8.0] Build #968: 5087-Fuel-should-be-out-of-Morphic-baseline-

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #968 was: SUCCESS. The Pull Request #5095 was integrated: "5087-Fuel-should-be-out-of-Morphic-baseline-" Pull request url: https://github.com/pharo-project/pharo/pull/5095 Issue Url: https://github.com/pharo-project/pharo/issues/5087 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 11, 2019

[Pharo 8.0] Build #967: Some-cleanings-on-protocols

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #967 was: FAILURE. The Pull Request #5115 was integrated: "Some-cleanings-on-protocols" Pull request url: https://github.com/pharo-project/pharo/pull/5115 Issue Url: https://github.com/pharo-project/pharo/issues/Some Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 11, 2019

[Pharo 8.0] Build #966: CompletionContextAndModelMerge

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #966 was: SUCCESS. The Pull Request #5109 was integrated: "CompletionContextAndModelMerge" Pull request url: https://github.com/pharo-project/pharo/pull/5109 Issue Url: https://github.com/pharo-project/pharo/issues/CompletionContextAndModelMerge Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 11, 2019

[Pharo 8.0] Build #965: 5093-Remove-Smart-Suggestions

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #965 was: SUCCESS. The Pull Request #5094 was integrated: "5093-Remove-Smart-Suggestions" Pull request url: https://github.com/pharo-project/pharo/pull/5094 Issue Url: https://github.com/pharo-project/pharo/issues/5093 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 9, 2019

[Pharo 8.0] Build #964: 5110-remove-smartSuggestions-classes

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #964 was: FAILURE. The Pull Request #5111 was integrated: "5110-remove-smartSuggestions-classes" Pull request url: https://github.com/pharo-project/pharo/pull/5111 Issue Url: https://github.com/pharo-project/pharo/issues/5110 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 8, 2019

[Pharo 8.0] Build #963: 3817-Unify-browseObsoleteMethodReferences--browseObsoleteReferences

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #963 was: SUCCESS. The Pull Request #5100 was integrated: "3817-Unify-browseObsoleteMethodReferences--browseObsoleteReferences" Pull request url: https://github.com/pharo-project/pharo/pull/5100 Issue Url: https://github.com/pharo-project/pharo/issues/3817 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 8, 2019

[Pharo 8.0] Build #962: Compiler: #parse should not do the doit wrapping

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #962 was: SUCCESS. The Pull Request #5098 was integrated: "Compiler: #parse should not do the doit wrapping" Pull request url: https://github.com/pharo-project/pharo/pull/5098 Issue Url: https://github.com/pharo-project/pharo/issues/CompilerParseNoWrapDoit Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 8, 2019

Re: [Pharo-dev] Moz2d Vs. Skia

by ducasse

Tx doru! > On 8 Nov 2019, at 11:41, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi > > Thanks for following the development of Bloc :). > > We invest in multiple backends because of several reasons. For example, for window hosting we have SDL2 (which relies on polling) and Glutin (which relies on a push model), but we also have Morphic. And now, when it comes to rendering we have both Moz2D and Skia. These have different properties. > > When we started to work with Moz2D, it was the only cross-platform vector graphical framework with rich support of text rendering. We knew that we eventually need to move away from it, but it allowed us to bootstrap nicely. At that time Skia was actually one of the backends of Moz2D. In the meantime, Skia evolved significantly. It hasnât quite reach the level of Moz2D when it comes to text yet, but for our typical use cases, it is already good enough. > > While Moz2D works fine today, we now want to move to Skia because of maintenance and support for newer technologies. For example, both Moz2D and Skia are written in C++ which mean we can not directly use both of them via FFI and have to implement C ABI bindings anyway. However, for Skia, there exists a project (https://github.com/rust-skia/rust-skia) that provides an up-to-date Skia bindings in Rust. This provides a quick way to build and to integrate into CI, and it also looks memory safe. Skia also has support for Vulkan. > > Now, while we target Skia in the short term, we also consider and play with other combinations. In particular, WebRenderer looks interesting. For text, we could use Skia, or we could also consider using something like font-kit. > > I wanted to detail a bit how we work to show how we exercise the underlying architecture continuously. A similar story happens on the host side. We think it is critical to have as much flexibility as possible at that level, while also exposing all underlying abilities in the image. For example, an important piece when dealing with text is to have access to accurate measurements. So, those are available through Sparta. > > Cheers, > Doru > > >> On Nov 7, 2019, at 6:52 AM, ducasse <stepharo(a)netcourrier.com> wrote: >> >> Hi doru and alex >> >> Can you tell me why you drop Moz2D and switch to Skia (which to us looks a much safer path starting from the packaging :)? >> >> S >> >> >> > > -- > feenk.com > > "Quality cannot be an afterthought." > >

Nov. 8, 2019

[Pharo 8.0] Build #961: Fix-bug-in-MCClassTraitDefinition

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #961 was: FAILURE. The Pull Request #5099 was integrated: "Fix-bug-in-MCClassTraitDefinition" Pull request url: https://github.com/pharo-project/pharo/pull/5099 Issue Url: https://github.com/pharo-project/pharo/issues/FIx Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 8, 2019

[Pharo 8.0] Build #960: Compiler API: turn forSyntaxHighlighting into an option

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #960 was: SUCCESS. The Pull Request #5082 was integrated: "Compiler API: turn forSyntaxHighlighting into an option" Pull request url: https://github.com/pharo-project/pharo/pull/5082 Issue Url: https://github.com/pharo-project/pharo/issues/CompilerAPICodeCompletion Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 8, 2019

Re: [Pharo-dev] Moz2d Vs. Skia

by Tudor Girba

Hi Thanks for following the development of Bloc :). We invest in multiple backends because of several reasons. For example, for window hosting we have SDL2 (which relies on polling) and Glutin (which relies on a push model), but we also have Morphic. And now, when it comes to rendering we have both Moz2D and Skia. These have different properties. When we started to work with Moz2D, it was the only cross-platform vector graphical framework with rich support of text rendering. We knew that we eventually need to move away from it, but it allowed us to bootstrap nicely. At that time Skia was actually one of the backends of Moz2D. In the meantime, Skia evolved significantly. It hasnât quite reach the level of Moz2D when it comes to text yet, but for our typical use cases, it is already good enough. While Moz2D works fine today, we now want to move to Skia because of maintenance and support for newer technologies. For example, both Moz2D and Skia are written in C++ which mean we can not directly use both of them via FFI and have to implement C ABI bindings anyway. However, for Skia, there exists a project (https://github.com/rust-skia/rust-skia) that provides an up-to-date Skia bindings in Rust. This provides a quick way to build and to integrate into CI, and it also looks memory safe. Skia also has support for Vulkan. Now, while we target Skia in the short term, we also consider and play with other combinations. In particular, WebRenderer looks interesting. For text, we could use Skia, or we could also consider using something like font-kit. I wanted to detail a bit how we work to show how we exercise the underlying architecture continuously. A similar story happens on the host side. We think it is critical to have as much flexibility as possible at that level, while also exposing all underlying abilities in the image. For example, an important piece when dealing with text is to have access to accurate measurements. So, those are available through Sparta. Cheers, Doru > On Nov 7, 2019, at 6:52 AM, ducasse <stepharo(a)netcourrier.com> wrote: > > Hi doru and alex > > Can you tell me why you drop Moz2D and switch to Skia (which to us looks a much safer path starting from the packaging :)? > > S > > > -- feenk.com "Quality cannot be an afterthought."

Nov. 8, 2019

[Pharo 8.0] Build #959: Clean Display packages group dependencies

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #959 was: SUCCESS. The Pull Request #5092 was integrated: "Clean Display packages group dependencies" Pull request url: https://github.com/pharo-project/pharo/pull/5092 Issue Url: https://github.com/pharo-project/pharo/issues/displayDependencies1 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 7, 2019

[Pharo 8.0] Build #958: 5017-should-have-a-setting-to-select-the-prettyprinter

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #958 was: FAILURE. The Pull Request #5091 was integrated: "5017-should-have-a-setting-to-select-the-prettyprinter" Pull request url: https://github.com/pharo-project/pharo/pull/5091 Issue Url: https://github.com/pharo-project/pharo/issues/5017 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 7, 2019

Re: [Pharo-dev] Horizontal scrolling in FastTable

by ducasse

thanks danil esteban is working on FastTable right now. So I imagine that he will have a look at your enh. Could you open a bug entry and issue a PR so that it does not get lost in email? Stef > On 7 Nov 2019, at 17:53, Danil Osipchuk <danil.osipchuk(a)gmail.com> wrote: > > As a followup, attached is a changeset for Pharo8 with a simple implementation of horizontal scrolling. I tried to keep it minimal. > It adds startColumnIndex var to FTTableContainerMorph which is being set when FTTableContainerMorph>>adjustToHorizontalScrollBarValue: is triggered. > The main change is in #calculateColumnWidths - it starts distributing space width from the startColumnIndex to ensure this area gets most visibility. If startColumnIndex is 0, it reverts to old (current) behavior - trying to draw columns starting from the first one as space permits. > > The scrolling thus jumps to a beginning of the column and I'm not particularly proud of the thing, but it is better then nothing and suits my immediate needs. So may be it is worth a look for those who are interested. > > To try one can use an example: > FTExamples exampleTableHorizontalScroll > > Or even set trialHSB := true in FTTableMorth>>initialize (like I have to enable it everywhere by default) > (as a side note the list is very quiet, compared to what it used to be years ago) > > Ð¿Ð½, 4 Ð½Ð¾ÑÐ±. 2019 Ð³. Ð² 14:14, Danil Osipchuk <danil.osipchuk(a)gmail.com <mailto:danil.osipchuk@gmail.com>>: > Hi all > > I wonder what is happening to the horizontal scrolling in FastTable, the stub is there for years (I've checked the latest 8.0). > I need it rather badly, could someone advise what is the hindrance there? I would try doing it myself, but I've never was doing much of UI programming and only recently returned to Pharo again, so have to catch up (a lot of things changed for good). > > How difficult would be to adopt vertical scrolling approach (which seems to be the same problem already solved to layperson ) > > > horizontalScrollBarValue: aNumber > trialHSB ifNotNil: [ > self inform: 'FTTableMorph>>#horizontalScrollBarValue: ', aNumber printString , String cr, > 'Does nothing yet.' , String cr, 'Need some advise here.' > ]. > > regards, > Danil > <FastTableHorizontalScrolling.cs>

Nov. 7, 2019

Re: [Pharo-dev] [ANN] Roadmap progress report October 2019 - Open meeting 14/11 16h EU

by Alexandre Bergel

Impressive work Esteban! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On 07-11-2019, at 12:47, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > EstebanLM wrote >> This is the log of what we have been working on last month. > > Wow, that's quite a list! Some of those have been on the wishlist for a > loooong time. Thanks and keep it up :) > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Nov. 7, 2019

[Pharo 8.0] Build #957: MCClassTraitDefinition-should-take-category-into-account-for-equality

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #957 was: FAILURE. The Pull Request #5072 was integrated: "MCClassTraitDefinition-should-take-category-into-account-for-equality" Pull request url: https://github.com/pharo-project/pharo/pull/5072 Issue Url: https://github.com/pharo-project/pharo/issues/MCClassTraitDefinition Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 7, 2019

Re: [Pharo-dev] Horizontal scrolling in FastTable

by Danil Osipchuk

As a followup, attached is a changeset for Pharo8 with a simple implementation of horizontal scrolling. I tried to keep it minimal. It adds startColumnIndex var to FTTableContainerMorph which is being set when FTTableContainerMorph>>adjustToHorizontalScrollBarValue: is triggered. The main change is in #calculateColumnWidths - it starts distributing space width from the startColumnIndex to ensure this area gets most visibility. If startColumnIndex is 0, it reverts to old (current) behavior - trying to draw columns starting from the first one as space permits. The scrolling thus jumps to a beginning of the column and I'm not particularly proud of the thing, but it is better then nothing and suits my immediate needs. So may be it is worth a look for those who are interested. To try one can use an example: FTExamples exampleTableHorizontalScroll Or even set trialHSB := true in FTTableMorth>>initialize (like I have to enable it everywhere by default) (as a side note the list is very quiet, compared to what it used to be years ago) Ð¿Ð½, 4 Ð½Ð¾ÑÐ±. 2019 Ð³. Ð² 14:14, Danil Osipchuk <danil.osipchuk(a)gmail.com>: > Hi all > > I wonder what is happening to the horizontal scrolling in FastTable, the > stub is there for years (I've checked the latest 8.0). > I need it rather badly, could someone advise what is the hindrance there? > I would try doing it myself, but I've never was doing much of UI > programming and only recently returned to Pharo again, so have to catch up > (a lot of things changed for good). > > How difficult would be to adopt vertical scrolling approach (which seems > to be the same problem already solved to layperson ) > > > horizontalScrollBarValue: aNumber > trialHSB ifNotNil: [ > self inform: 'FTTableMorph>>#horizontalScrollBarValue: ', aNumber > printString , String cr, > 'Does nothing yet.' , String cr, 'Need some advise here.' > ]. > > regards, > Danil >

Nov. 7, 2019

[Pharo 8.0] Build #956: Clean Compiler external dependencies

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #956 was: FAILURE. The Pull Request #5068 was integrated: "Clean Compiler external dependencies" Pull request url: https://github.com/pharo-project/pharo/pull/5068 Issue Url: https://github.com/pharo-project/pharo/issues/compilerDependencies1 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 7, 2019

Re: [Pharo-dev] [ANN] Roadmap progress report October 2019 - Open meeting 14/11 16h EU

by Sean P. DeNigris

EstebanLM wrote > This is the log of what we have been working on last month. Wow, that's quite a list! Some of those have been on the wishlist for a loooong time. Thanks and keep it up :) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Nov. 7, 2019

[Pharo 8.0] Build #955: Fix for FullBlockClosure

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #955 was: SUCCESS. The Pull Request #5076 was integrated: "Fix for FullBlockClosure" Pull request url: https://github.com/pharo-project/pharo/pull/5076 Issue Url: https://github.com/pharo-project/pharo/issues/FixesFullBlockClosure Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 7, 2019

Internship for a Master research in computer science

by Jannik Laval

Dear colleagues, You will find, in the following link, a proposal for a Master research in computer science or equivalent, for February 2020 at the DISP laboratory, Lyon. https://www.disp-lab.fr/?q=fr/content/stage-m2-banc-de-tests-d%E2%80%99%C3%… <https://www.disp-lab.fr/?q=fr/content/stage-m2-banc-de-tests-d%E2%80%99%C3%…> Best regards -- ~~Jannik Laval~~ Enseignant-chercheur Responsable PÃ©dagogique Licence Coordonnateur de Projet en SystÃ¨mes d'Information IUT LumiÃ¨re, UniversitÃ© LumiÃ¨re Lyon 2 laboratoire DISP +33 4 78 77 43 06 http://www.jannik-laval.eu <http://www.jannik-laval.eu/> http://www.phratch.com <http://www.phratch.com/> http://www.approchealpes.info <http://www.approchealpes.info/>

Nov. 7, 2019

[Pharo 7.0] Build #173: 5077-Add-byteAt-as-alias-to-digitAt-to-Integer-in-Pharo-7-to-support-forward-compatibility-with-Pharo-8

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #173 was: SUCCESS. The Pull Request #5079 was integrated: "5077-Add-byteAt-as-alias-to-digitAt-to-Integer-in-Pharo-7-to-support-forward-compatibility-with-Pharo-8" Pull request url: https://github.com/pharo-project/pharo/pull/5079 Issue Url: https://pharo.fogbugz.com/f/cases/5077 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 7, 2019