- Pharo-dev - lists.pharo.org

GTDebugger - class variables

by Ben Coman

I just noticed it seems class variables are not shown in Variables pane of GTDebugger. It confused me for a while, and I expect it would be troubling for newcomers. Is this due to copying the previous Debugger functionality here, or some other design decision? Any reason to not display class variables in the Variable pane? cheers -ben

July 3, 2016

Re: [Pharo-dev] Bug in MailA

by Ben Coman

On Sun, Jul 3, 2016 at 7:25 PM, Bernhard Pieber <bernhard(a)pieber.com> wrote: > Done! Thanks Bernhard, but I can't find the issue in the tracker. Can you paste a link? On Sun, Jul 3, 2016 at 7:41 PM, Bernhard Pieber <bernhard(a)pieber.com> wrote: > I wonder about the process for fixes for Pharo 4.0? Is it the same? If Iâd put the equivalent fix into the Pharo40Inbox, would it be integrated? I am not familiar with the release process, but apparently there is a fair amount of manual work to do each release. Typically it seems each major release is followed by one minor point release about 6 months later. So 4.0 is probably too far back for another release. It would be good however if there was some community process to manage fixes for very old releases. Perhaps there could be a tag like "Pharo4-hotfix" in Fogbugz, so users of their own accord could search for community fixes contributed long after the main development focus has moved on - to be used at own risk. This might provide better sustainability for older releases without drawing resources from the latest version. That is, Pharo 4.0 users would need to rely on review by other Pharo 4.0 user to review and promote their fixes to "hotfix" - but at least the Fogbugz facilitates the collaboration. This might also work for 5.0 fixes as a state between Work Needed and Closed Fix Integrated while they are waiting to be rolled up into the point release. cheers -ben > > Cheers, > Bernhard > >> Am 03.07.2016 um 08:46 schrieb stepharo <stepharo(a)free.fr>: >> >> Thanks Bernhard >> >> - can you open a bug entry? >> >> - publish a slice? (press slice + bug number) >> >> Our integration tool and process work this way >> >> Stef >> >> Le 2/7/16 Ã 21:16, Bernhard Pieber a Ã©crit : >>> Hi, >>> >>> The following code goes into an endless loop: >>> MailAddressParser addressesIn: 'romeo&julia@verona.itâ >>> >>> Itâs because of the ampersand. The fix is trivial, because the bug just was a typo. >>> >>> Fix and test are in the Pharo50Inbox: >>> Network-Mail-BernhardPieber.46.mcz >>> Network-Tests-BernhardPieber.14.mcz > >

July 3, 2016

Re: [Pharo-dev] Bug in MailA

by Sven Van Caekenberghe

Thank you. > On 03 Jul 2016, at 13:25, Bernhard Pieber <bernhard(a)pieber.com> wrote: > > Done! > > Cheers, > Bernhard > >> Am 03.07.2016 um 00:08 schrieb Ben Coman <btc(a)openinworld.com>: >> >> On Sun, Jul 3, 2016 at 3:16 AM, Bernhard Pieber <bernhard(a)pieber.com> wrote: >>> Hi, >>> >>> The following code goes into an endless loop: >>> MailAddressParser addressesIn: 'romeo&julia@verona.itâ >>> >>> Itâs because of the ampersand. The fix is trivial, because the bug just was a typo. >>> >>> Fix and test are in the Pharo50Inbox: >>> Network-Mail-BernhardPieber.46.mcz >>> Network-Tests-BernhardPieber.14.mcz >>> >>> Cheers, >>> Bernhard >> >> Thanks Bernhard. >> Can you log an issue for it on >> and submit this in Slice format. >> Instructions at http://pharo.org/contribute-propose-fix >> This makes it easier to review and the integration system only works >> with Slices & Configurations. >> >> cheers -ben > >

July 3, 2016

Re: [Pharo-dev] Bug in MailA

by Bernhard Pieber

I wonder about the process for fixes for Pharo 4.0? Is it the same? If Iâd put the equivalent fix into the Pharo40Inbox, would it be integrated? Cheers, Bernhard > Am 03.07.2016 um 08:46 schrieb stepharo <stepharo(a)free.fr>: > > Thanks Bernhard > > - can you open a bug entry? > > - publish a slice? (press slice + bug number) > > Our integration tool and process work this way > > Stef > > Le 2/7/16 Ã 21:16, Bernhard Pieber a Ã©crit : >> Hi, >> >> The following code goes into an endless loop: >> MailAddressParser addressesIn: 'romeo&julia@verona.itâ >> >> Itâs because of the ampersand. The fix is trivial, because the bug just was a typo. >> >> Fix and test are in the Pharo50Inbox: >> Network-Mail-BernhardPieber.46.mcz >> Network-Tests-BernhardPieber.14.mcz

July 3, 2016

Re: [Pharo-dev] Bug in MailA

by Bernhard Pieber

Done! Cheers, Bernhard > Am 03.07.2016 um 00:08 schrieb Ben Coman <btc(a)openinworld.com>: > > On Sun, Jul 3, 2016 at 3:16 AM, Bernhard Pieber <bernhard(a)pieber.com> wrote: >> Hi, >> >> The following code goes into an endless loop: >> MailAddressParser addressesIn: 'romeo&julia@verona.itâ >> >> Itâs because of the ampersand. The fix is trivial, because the bug just was a typo. >> >> Fix and test are in the Pharo50Inbox: >> Network-Mail-BernhardPieber.46.mcz >> Network-Tests-BernhardPieber.14.mcz >> >> Cheers, >> Bernhard > > Thanks Bernhard. > Can you log an issue for it on > and submit this in Slice format. > Instructions at http://pharo.org/contribute-propose-fix > This makes it easier to review and the integration system only works > with Slices & Configurations. > > cheers -ben

July 3, 2016

Re: [Pharo-dev] Bug in MailA

by Ben Coman

On Sun, Jul 3, 2016 at 6:08 AM, Ben Coman <btc(a)openinworld.com> wrote: > On Sun, Jul 3, 2016 at 3:16 AM, Bernhard Pieber <bernhard(a)pieber.com> wrote: >> Hi, >> >> The following code goes into an endless loop: >> MailAddressParser addressesIn: 'romeo&julia@verona.itâ >> >> Itâs because of the ampersand. The fix is trivial, because the bug just was a typo. >> >> Fix and test are in the Pharo50Inbox: >> Network-Mail-BernhardPieber.46.mcz >> Network-Tests-BernhardPieber.14.mcz >> >> Cheers, >> Bernhard >> >> >> > > Thanks Bernhard. > Can you log an issue for it on > and submit this in Slice format. > Instructions at http://pharo.org/contribute-propose-fix > This makes it easier to review and the integration system only works > with Slices & Configurations. > > cheers -ben P.S. Once your Slice is integrated, see instructions at the bottom of [1] to get yourself added to the contributors page. [1] http://pharo.org/about cheers -ben

July 3, 2016

Re: [Pharo-dev] Bug in MailA

by stepharo

Thanks Bernhard - can you open a bug entry? - publish a slice? (press slice + bug number) Our integration tool and process work this way Stef Le 2/7/16 Ã 21:16, Bernhard Pieber a Ã©crit : > Hi, > > The following code goes into an endless loop: > MailAddressParser addressesIn: 'romeo&julia@verona.itâ > > Itâs because of the ampersand. The fix is trivial, because the bug just was a typo. > > Fix and test are in the Pharo50Inbox: > Network-Mail-BernhardPieber.46.mcz > Network-Tests-BernhardPieber.14.mcz > > Cheers, > Bernhard > > > >

July 3, 2016

Re: [Pharo-dev] Bug in MailA

by Ben Coman

On Sun, Jul 3, 2016 at 3:16 AM, Bernhard Pieber <bernhard(a)pieber.com> wrote: > Hi, > > The following code goes into an endless loop: > MailAddressParser addressesIn: 'romeo&julia@verona.itâ > > Itâs because of the ampersand. The fix is trivial, because the bug just was a typo. > > Fix and test are in the Pharo50Inbox: > Network-Mail-BernhardPieber.46.mcz > Network-Tests-BernhardPieber.14.mcz > > Cheers, > Bernhard > > > Thanks Bernhard. Can you log an issue for it on and submit this in Slice format. Instructions at http://pharo.org/contribute-propose-fix This makes it easier to review and the integration system only works with Slices & Configurations. cheers -ben

July 2, 2016

Bug in MailA

by Bernhard Pieber

Hi, The following code goes into an endless loop: MailAddressParser addressesIn: 'romeo&julia@verona.itâ Itâs because of the ampersand. The fix is trivial, because the bug just was a typo. Fix and test are in the Pharo50Inbox: Network-Mail-BernhardPieber.46.mcz Network-Tests-BernhardPieber.14.mcz Cheers, Bernhard

July 2, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60132 Home: https://github.com/pharo-project/pharo-core

July 2, 2016