- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #96: Small fix that slightly improves how the removal caption is createdâ¦

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

There is a new Pharo build available! The status of the build #96 was: SUCCESS. The Pull Request #2673 was integrated: "Small fix that slightly improves how the removal caption is createdâ¦" Pull request url: https://github.com/pharo-project/pharo/pull/2673 Issue Url: https://pharo.fogbugz.com/f/cases/2567 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 22, 2019

[Pharo 8.0] Build #95: 1967-critiques-icons-are-not-managed-correctly

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

There is a new Pharo build available! The status of the build #95 was: SUCCESS. The Pull Request #2655 was integrated: "1967-critiques-icons-are-not-managed-correctly" Pull request url: https://github.com/pharo-project/pharo/pull/2655 Issue Url: https://pharo.fogbugz.com/f/cases/1967 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 22, 2019

[Pharo 8.0] Build #94: 2683-Remove-deprecated-pragma-to-use-deprecated-method

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

There is a new Pharo build available! The status of the build #94 was: SUCCESS. The Pull Request #2686 was integrated: "2683-Remove-deprecated-pragma-to-use-deprecated-method" Pull request url: https://github.com/pharo-project/pharo/pull/2686 Issue Url: https://pharo.fogbugz.com/f/cases/2683 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 22, 2019

Remember to registrar to Pharo days 2019!

by Esteban Lorenzano

Dear all, Pharo days registration is open since two weeks now, and we are starting to work on the schedule and organising the social event :) Register now! Pharo days is a gathering of the Pharo community to exchange, discuss and code with your online colleagues. Join us to share your experiences and help to make a better Pharo! To register, please proceed to the Pharo Days 2019 web page: https://pharo.org/2019PharoDays <https://pharo.org/2019PharoDays>, or go directly to the association event: https://association.pharo.org/event-3255426 <https://association.pharo.org/event-3255426>. (Yes, the schedule is still to be defined, stay tuned). If there are any questions or problems, I am happy to answer them. Esteban

Feb. 22, 2019

[Pharo 8.0] Build #93: 2670-Update-the-checkVMVersion-date

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

There is a new Pharo build available! The status of the build #93 was: SUCCESS. The Pull Request #2671 was integrated: "2670-Update-the-checkVMVersion-date" Pull request url: https://github.com/pharo-project/pharo/pull/2671 Issue Url: https://pharo.fogbugz.com/f/cases/2670 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 22, 2019

[Pharo 8.0] Build #92: 2668-Improve-some-randomly-failing-test-to-give-better-trace

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

There is a new Pharo build available! The status of the build #92 was: SUCCESS. The Pull Request #2669 was integrated: "2668-Improve-some-randomly-failing-test-to-give-better-trace" Pull request url: https://github.com/pharo-project/pharo/pull/2669 Issue Url: https://pharo.fogbugz.com/f/cases/2668 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 22, 2019

Re: [Pharo-dev] [Glass] Bug in Regex?

by Max Leske

On 21 Feb 2019, at 16:25, Mariano Martinez Peck wrote: > Hi Max, > > I opened this case [1] with the explanation and the fix. If you can give it > a try, that would be great. I would also like to improve the test I wrote, > so if you have more edge cases or ideas I can assert, let me know. Great. I'll take a look when I get a chance. > > [1] https://github.com/pharo-project/pharo/issues/2679 > > Cheers, > > > On Thu, Feb 21, 2019 at 10:44 AM Max Leske <maxleske(a)gmail.com> wrote: > >> On 21 Feb 2019, at 13:40, Mariano Martinez Peck wrote: >> >>> Vassili Bykov Hi Max, >>> >>> It looks like it was fixed on a later version of VBRegex. I was able >>> to >>> extract the 2 little changes to make it work. Do you know if there is >>> an >>> issue already open for this so that I can submit the changes? >>> >>> BTW, I am trying to understand the history of Regex. It's clear that >>> the >>> original implementation was done by Vassili Bykov and the packages >>> were >>> called VBRegex and that was in VW under the Public Store. I guess, at >>> some >>> point, that code was ported to Pharo. In Pharo 1.1 the packages are >>> still >>> called 'VB-Regex' but on recent ones its called "Regex". >>> >> >> The package name changed between Pharo 1.1.2 and Pharo 1.2.2, as far as >> I can tell from the images I have on my machine. >> >>> What I cannot confirm is which version Pharo (or maybe this was even >>> en >>> Squeak before Pharo forked) ported from VW. All I could find is a >>> class >>> comment on RxMatcher saying "-- Regular Expression Matcher v 1.1 (C) >>> 1996, >>> 1999 Vassili Bykov". As you can see, that is 1999. VW has newer >>> versions >>> from 1.2.x to 1.4.x, latest commit being on 2014. >> >> The oldest images I have is Squeak3.9 of 7 November 2006 update 7067, >> and that already contains VBRegex. >> >>> >>> The particular problem we are discussing in this thread was fixed in >>> 1.3.1. >>> >>> So I am not sure if someone ever tried porting again a newer version >>> to >>> Pharo? It doesn't seem the case. >> >> It would certainly be great to get those fixes! >> >>> >>> Anyone knows a bit more the history here? >>> >>> Thanks >>> >>> >>> On Thu, Feb 21, 2019 at 5:18 AM Max Leske <maxleske(a)gmail.com> wrote: >>> >>>> Hi Mariano, >>>> >>>> Yes, there is indeed such a bug (if it hasn't been fixed in an update >>>> to >>>> VBRegex that is). The bug is simple to work around though, as all you >>>> have >>>> to do is sort your branch (|) terms by length. Here's the comment >>>> I've >>>> written for a regex generating method is use: >>>> >>>> " The sorting is very important because VB-Regex aborts early on >>>> branches. >>>> Example: 'bl' matchesRegex: 'b|bl' --> false The solution is to sort >>>> by >>>> length (longest first), then alphabetically, with the short group >>>> optimization at the end. " >>>> >>>> Cheers, >>>> Max >>>> >>>> On 21 Feb 2019, at 3:33, Mariano Martinez Peck wrote: >>>> >>>> >>>> >>>> On Wed, Feb 20, 2019 at 5:56 PM Esteban Maringolo via Glass < >>>> glass(a)lists.gemtalksystems.com> wrote: >>>> >>>>> What a good case to have GToolkit visualizations help debugging this >>>>> RX >>>>> tree ;) >>>>> >>>>> >>>> Oh yeah..And look Doru, they have some stuff on the top right >>>> "Explanation" panel: https://regex101.com/r/MqVXz8/1 >>>> >>>> >>>> -- >>>> Mariano >>>> https://twitter.com/MartinezPeck >>>> http://marianopeck.wordpress.com >>>> >>>> >>> >>> -- >>> Mariano >>> https://twitter.com/MartinezPeck >>> http://marianopeck.wordpress.com >> >> >> >> > > -- > Mariano > https://twitter.com/MartinezPeck > http://marianopeck.wordpress.com

Feb. 22, 2019

Re: [Pharo-dev] [Glass] Bug in Regex?

by Tim Mackinnon

Nice bit of detective work ! Sent from my iPhone > On 21 Feb 2019, at 15:25, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > Hi Max, > > I opened this case [1] with the explanation and the fix. If you can give it a try, that would be great. I would also like to improve the test I wrote, so if you have more edge cases or ideas I can assert, let me know. > > [1] https://github.com/pharo-project/pharo/issues/2679 > > Cheers, > > >> On Thu, Feb 21, 2019 at 10:44 AM Max Leske <maxleske(a)gmail.com> wrote: >> On 21 Feb 2019, at 13:40, Mariano Martinez Peck wrote: >> >> > Vassili Bykov Hi Max, >> > >> > It looks like it was fixed on a later version of VBRegex. I was able >> > to >> > extract the 2 little changes to make it work. Do you know if there is >> > an >> > issue already open for this so that I can submit the changes? >> > >> > BTW, I am trying to understand the history of Regex. It's clear that >> > the >> > original implementation was done by Vassili Bykov and the packages >> > were >> > called VBRegex and that was in VW under the Public Store. I guess, at >> > some >> > point, that code was ported to Pharo. In Pharo 1.1 the packages are >> > still >> > called 'VB-Regex' but on recent ones its called "Regex". >> > >> >> The package name changed between Pharo 1.1.2 and Pharo 1.2.2, as far as >> I can tell from the images I have on my machine. >> >> > What I cannot confirm is which version Pharo (or maybe this was even >> > en >> > Squeak before Pharo forked) ported from VW. All I could find is a >> > class >> > comment on RxMatcher saying "-- Regular Expression Matcher v 1.1 (C) >> > 1996, >> > 1999 Vassili Bykov". As you can see, that is 1999. VW has newer >> > versions >> > from 1.2.x to 1.4.x, latest commit being on 2014. >> >> The oldest images I have is Squeak3.9 of 7 November 2006 update 7067, >> and that already contains VBRegex. >> >> > >> > The particular problem we are discussing in this thread was fixed in >> > 1.3.1. >> > >> > So I am not sure if someone ever tried porting again a newer version >> > to >> > Pharo? It doesn't seem the case. >> >> It would certainly be great to get those fixes! >> >> > >> > Anyone knows a bit more the history here? >> > >> > Thanks >> > >> > >> > On Thu, Feb 21, 2019 at 5:18 AM Max Leske <maxleske(a)gmail.com> wrote: >> > >> >> Hi Mariano, >> >> >> >> Yes, there is indeed such a bug (if it hasn't been fixed in an update >> >> to >> >> VBRegex that is). The bug is simple to work around though, as all you >> >> have >> >> to do is sort your branch (|) terms by length. Here's the comment >> >> I've >> >> written for a regex generating method is use: >> >> >> >> " The sorting is very important because VB-Regex aborts early on >> >> branches. >> >> Example: 'bl' matchesRegex: 'b|bl' --> false The solution is to sort >> >> by >> >> length (longest first), then alphabetically, with the short group >> >> optimization at the end. " >> >> >> >> Cheers, >> >> Max >> >> >> >> On 21 Feb 2019, at 3:33, Mariano Martinez Peck wrote: >> >> >> >> >> >> >> >> On Wed, Feb 20, 2019 at 5:56 PM Esteban Maringolo via Glass < >> >> glass(a)lists.gemtalksystems.com> wrote: >> >> >> >>> What a good case to have GToolkit visualizations help debugging this >> >>> RX >> >>> tree ;) >> >>> >> >>> >> >> Oh yeah..And look Doru, they have some stuff on the top right >> >> "Explanation" panel: https://regex101.com/r/MqVXz8/1 >> >> >> >> >> >> -- >> >> Mariano >> >> https://twitter.com/MartinezPeck >> >> http://marianopeck.wordpress.com >> >> >> >> >> > >> > -- >> > Mariano >> > https://twitter.com/MartinezPeck >> > http://marianopeck.wordpress.com >> >> >> > > > -- > Mariano > https://twitter.com/MartinezPeck > http://marianopeck.wordpress.com

Feb. 22, 2019

[ANN] ba-st Web stack updated (RenoirSt, Willow and HighchartsSt)

by Gabriel Cotelli

Now that Pharo 7 is finally released, we took some time to update the whole web stack hosted at ba-st <https://github.com/ba-st>. As a general update all the projects now follow the brand new community guidelines <https://github.com/ba-st/Community> and support Pharo 6.1â32 bits and Pharo 7â32 & 64 bits. The build matrix now includes Pharo 8 as a preview. This includes new versions of RenoirSt, HighchartsSt, Boardwalk, Willow and it's related projects. You can see the detailed announcement here <https://medium.com/ba-st/web-stack-summer-release-1d141b2660ee>. Regards, Gabriel

Feb. 21, 2019

[ANN] Pharo Consortium New Academic Member: TecnolÃ³gico de Monterrey in Guadalajara

by Marcus Denker

The Pharo Consortium is very happy to announce that TecnolÃ³gico de Monterrey in Guadalajara has joined the Consortium as an Academic Member. About - TecnolÃ³gico de Monterrey in Guadalajara: http://www.gda.itesm.mx - 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

Feb. 21, 2019