February 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] ||

by Marcus Denker

On Tue, Feb 3, 2015 at 7:06 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Marcus, > > thanks! When I visit the fogbugz page there's a line that says "slice > in inbox" but no link to any file containing the slice I can see. How do I > track down the slice file itself? > > The slice has the issue number as part of it's name. So you can just search for that in the inbox. To the the changes, sometimes I just download the version one before integration ( 40 #419 here) from http://files.pharo.org/image/40/ and do a merge there. Marcus > On Tue, Feb 3, 2015 at 9:48 AM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >> >> On 03 Feb 2015, at 18:36, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >> On 03 Feb 2015, at 09:17, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >> On 02 Feb 2015, at 21:47, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> >> Hi All, >> >> code as in the double bars forming the end of block arguments and the >> beginning of block temporaries in >> >> >> This is fixed in Pharo4 (I think we did that in Pharo3 already): >> >> I should search the issue in the issue trackerâ¦ it seems to be Pharo4, so >> just 1296 closed issues to check thereâ¦ >> I will search for it. >> >> It seems to be this one: >> >> https://pharo.fogbugz.com/f/cases/14630/Pipes-method-highlighting >> >> integrated in Pharo4 update #420 >> >> Marcus >> > > > > -- > best, > Eliot > -- -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Feb. 3, 2015

Re: [Pharo-dev] ||

by Eliot Miranda

Hi Marcus, thanks! When I visit the fogbugz page there's a line that says "slice in inbox" but no link to any file containing the slice I can see. How do I track down the slice file itself? On Tue, Feb 3, 2015 at 9:48 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 03 Feb 2015, at 18:36, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 03 Feb 2015, at 09:17, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 02 Feb 2015, at 21:47, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi All, > > code as in the double bars forming the end of block arguments and the > beginning of block temporaries in > > > This is fixed in Pharo4 (I think we did that in Pharo3 already): > > I should search the issue in the issue trackerâ¦ it seems to be Pharo4, so > just 1296 closed issues to check thereâ¦ > I will search for it. > > It seems to be this one: > > https://pharo.fogbugz.com/f/cases/14630/Pipes-method-highlighting > > integrated in Pharo4 update #420 > > Marcus > -- best, Eliot

Feb. 3, 2015

Re: [Pharo-dev] Overwrite repository in symbolic version

by Yuriy Tymchuk

Yes, I do the same, although instead of using \ I wrap my command in double quotes. Still I think that dedicated handler is nicer. Maybe Iâll do it one day. Uko > On 03 Feb 2015, at 18:32, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > I do on the command line the following: > > pharo Pharo.image eval --save Metacello new baseline: \'MyProject\'\; repository: \'github://\'\; load > > The \ are a bit annoying, but it gives you access to any smalltalk cod, which is very convenient. > > Thierry > > Le 3 fÃ©vr. 2015 17:15, "Yuriy Tymchuk" <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> a Ã©crit : > One more question. Is there any command line handler which uses Metacello? Because as far as I know, Gofer does not support github âprotocolâ. > > Uko > >> On 02 Feb 2015, at 18:28, Thierry Goubier <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: >> >> Hi Uko, >> >> 2015-02-02 17:34 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: >> Hi. >> >> Thank you in a first place. >> >> Maybe I should use baseline class instead of configuration indeed. But I also like to release some versions using git tags. Does it make sense to use baseline class for development purposes and configuration for releases. >> >> It's up to you. >> >> My suggestion would be baselines in the branches and version tags, and refer to those in a configuration. >> >> A baseline in a branch behaves like a #development version in a configuration; a baseline in a version tag behaves exactly like a #stable version in a configuration, except that you don't have to specify the precise version and file name for each package. >> >> Thierry >> >> >> Uko >> >> >>> On 01 Feb 2015, at 16:59, Thierry Goubier <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: >>> >>> Hi Uko, >>> >>> If I understand your need correctly, I would say yes : you can add a spec repository: anUrl inside the version and this should override the repository inside the baseline method. >>> >>> If you're ready to try some of the new stuff pushed in Metacello by Dale, I would suggest that you create a BaselineOfYourProject inside your branch and write a configuration which refer to the baseline; there, just changing the url to point to your branch would make it work. >>> >>> inside the version method, for example: (gitfiletree url) >>> >>> spec >>> blessing: #development; >>> author: 'ThierryGoubier'; >>> baseline: 'AltBrowser' >>> with: [ spec repository: 'gitfiletree://github.com/ThierryGoubier/AltBrowser.git?branch=pharo4.0 <http://github.com/ThierryGoubier/AltBrowser.git?branch=pharo4.0>' ]; >>> import: 'AltBrowser' >>> >>> (It's also quite convenient to be able to work with metacello scripts which are as short as loading the configuration in the first place: >>> >>> Metacello new >>> baseline: 'AltBrowser'; >>> repository: 'gitfiletree://github.com/ThierryGoubier/AltBrowser:pharo4.0 <http://github.com/ThierryGoubier/AltBrowser:pharo4.0>'; >>> load >>> >>> And you can then customize your dependencies per branches, by modifying the BaselineOf in each. >>> >>> Thierry >>> >>> >>> 2015-02-01 16:21 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: >>> Hi, >>> >>> Iâm using git for versioning, and usually I just work with master branch. Now I have created another branch, can I create at least temporal symbolic version that will work on a current baseline, but will use different ârepositoryâ and so other branch? Or is there another good way to handle branches? >>> >>> Uko >>> >> >> >

Feb. 3, 2015

Re: [Pharo-dev] ||

by Levente Uzonyi

On Tue, 3 Feb 2015, Marcus Denker wrote: > > On 03 Feb 2015, at 09:17, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 02 Feb 2015, at 21:47, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi All, > Â Â code as in the double bars forming the end of block arguments and the beginning of block temporaries in > > > This is fixed in Pharo4 (I think we did that in Pharo3 already): > > I should search the issue in the issue trackerâ¦ it seems to be Pharo4, so justÂ 1296 closed issues to check thereâ¦ > I will search for it. > > Another question: In the code I saw. ReadOnlyVariableBinding. I removed that in Pharo relatively early as it was not used: > half of the classesÂ were stored that binding (old ones) all newer ones where just associations. > The code to make aÂ binding "read only" was never called. > > Is this now used in Squeak? Is it worth the complexity? Squeak doesn't use ReadOnlyVariableBinding anymore. The bindings of classes are instances of the ClassBinding class. Without using separate class it's a bit cumbersome (and less OO) to decide if an assignment to a global variable should be allowed or not. E.g.: Foo := 1. should work if Foo is a global, but not a behavior. It should raise an error if it's a behavior. Levente > > Marcus > >

Feb. 3, 2015

Re: [Pharo-dev] GitFileTree - Git command not found (is which shell startup script is run when pharo launched from UI)

by Thierry Goubier

Hi Christophe, looks like that a configuration option for the path to the git command is necessary :) https://github.com/dalehenrich/filetree/issues/143 I'm planning a bit of a rewrite for GitFileTree (saw a few significant issues on Monticello to git integration pop-up recently) and I'll add that along with the others. Thierry 2015-02-03 16:08 GMT+01:00 Christophe Demarey <Christophe.Demarey(a)inria.fr>: > Hi, > > I wanted to give a try to gitfiletree but I got a 'Git command not found'. > Indeed, the git command is not in the path Here is the code used by > GitFileTree to run a git command: > > | c output | > [ > c := PipeableOSProcess > command: 'export'. > output := ReadStream on: c output. > c succeeded > ifFalse: [ self error: 'Git error: ' , c > errorPipelineContents ] ] > ensure: [ c closePipes ]. > output > > I replaced the command to execute by 'export' to get all environment > variables. I noticed that '/usr/local/bin' is not in the path (used by > brew). > > > To get my full environment (.profile executed), I need to run pharo from a > shell with the same environment. The question is: how to run Pharo from the > UI and get this environment? > I tried with a .bashrc, bash_profile without success. > Any idea? > > Thanks, > Christophe.

Feb. 3, 2015

Re: [Pharo-dev] ||

by Marcus Denker

> On 03 Feb 2015, at 18:36, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 03 Feb 2015, at 09:17, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >> >>> On 02 Feb 2015, at 21:47, Eliot Miranda <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>> wrote: >>> >>> Hi All, >>> >>> code as in the double bars forming the end of block arguments and the beginning of block temporaries in >>> >> >> This is fixed in Pharo4 (I think we did that in Pharo3 already): >> > I should search the issue in the issue trackerâ¦ it seems to be Pharo4, so just 1296 closed issues to check thereâ¦ > I will search for it. > It seems to be this one: https://pharo.fogbugz.com/f/cases/14630/Pipes-method-highlighting integrated in Pharo4 update #420 Marcus

Feb. 3, 2015

Re: [Pharo-dev] ||

by Marcus Denker

> On 03 Feb 2015, at 09:17, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 02 Feb 2015, at 21:47, Eliot Miranda <eliot.miranda(a)gmail.com <mailto:eliot.miranda@gmail.com>> wrote: >> >> Hi All, >> >> code as in the double bars forming the end of block arguments and the beginning of block temporaries in >> > > This is fixed in Pharo4 (I think we did that in Pharo3 already): > I should search the issue in the issue trackerâ¦ it seems to be Pharo4, so just 1296 closed issues to check thereâ¦ I will search for it. Another question: In the code I saw. ReadOnlyVariableBinding. I removed that in Pharo relatively early as it was not used: half of the classes were stored that binding (old ones) all newer ones where just associations. The code to make a binding "read only" was never called. Is this now used in Squeak? Is it worth the complexity? Marcus

Feb. 3, 2015

Re: [Pharo-dev] Overwrite repository in symbolic version

by Thierry Goubier

I do on the command line the following: pharo Pharo.image eval --save Metacello new baseline: \'MyProject\'\; repository: \'github://\'\; load The \ are a bit annoying, but it gives you access to any smalltalk cod, which is very convenient. Thierry Le 3 fÃ©vr. 2015 17:15, "Yuriy Tymchuk" <yuriy.tymchuk(a)me.com> a Ã©crit : > One more question. Is there any command line handler which uses Metacello? > Because as far as I know, Gofer does not support github "protocol". > > Uko > > On 02 Feb 2015, at 18:28, Thierry Goubier <thierry.goubier(a)gmail.com> > wrote: > > Hi Uko, > > 2015-02-02 17:34 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > >> Hi. >> >> Thank you in a first place. >> >> Maybe I should use baseline class instead of configuration indeed. But I >> also like to release some versions using git tags. Does it make sense to >> use baseline class for development purposes and configuration for releases. >> > > It's up to you. > > My suggestion would be baselines in the branches and version tags, and > refer to those in a configuration. > > A baseline in a branch behaves like a #development version in a > configuration; a baseline in a version tag behaves exactly like a #stable > version in a configuration, except that you don't have to specify the > precise version and file name for each package. > > Thierry > > >> >> Uko >> >> >> On 01 Feb 2015, at 16:59, Thierry Goubier <thierry.goubier(a)gmail.com> >> wrote: >> >> Hi Uko, >> >> If I understand your need correctly, I would say yes : you can add a spec >> repository: anUrl inside the version and this should override the >> repository inside the baseline method. >> >> If you're ready to try some of the new stuff pushed in Metacello by Dale, >> I would suggest that you create a BaselineOfYourProject inside your branch >> and write a configuration which refer to the baseline; there, just changing >> the url to point to your branch would make it work. >> >> inside the version method, for example: (gitfiletree url) >> >> spec >> blessing: #development; >> author: 'ThierryGoubier'; >> baseline: 'AltBrowser' >> with: [ spec repository: 'gitfiletree:// >> github.com/ThierryGoubier/AltBrowser.git?branch=pharo4.0' ]; >> import: 'AltBrowser' >> >> (It's also quite convenient to be able to work with metacello scripts >> which are as short as loading the configuration in the first place: >> >> Metacello new >> baseline: 'AltBrowser'; >> repository: 'gitfiletree:// >> github.com/ThierryGoubier/AltBrowser:pharo4.0'; >> load >> >> And you can then customize your dependencies per branches, by modifying >> the BaselineOf in each. >> >> Thierry >> >> >> 2015-02-01 16:21 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: >> >>> Hi, >>> >>> I'm using git for versioning, and usually I just work with master >>> branch. Now I have created another branch, can I create at least temporal >>> symbolic version that will work on a current baseline, but will use >>> different "repository" and so other branch? Or is there another good way to >>> handle branches? >>> >>> Uko >>> >> >> >> > >

Feb. 3, 2015

Re: [Pharo-dev] Overwrite repository in symbolic version

by Yuriy Tymchuk

One more question. Is there any command line handler which uses Metacello? Because as far as I know, Gofer does not support github âprotocolâ. Uko > On 02 Feb 2015, at 18:28, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Hi Uko, > > 2015-02-02 17:34 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: > Hi. > > Thank you in a first place. > > Maybe I should use baseline class instead of configuration indeed. But I also like to release some versions using git tags. Does it make sense to use baseline class for development purposes and configuration for releases. > > It's up to you. > > My suggestion would be baselines in the branches and version tags, and refer to those in a configuration. > > A baseline in a branch behaves like a #development version in a configuration; a baseline in a version tag behaves exactly like a #stable version in a configuration, except that you don't have to specify the precise version and file name for each package. > > Thierry > > > Uko > > >> On 01 Feb 2015, at 16:59, Thierry Goubier <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: >> >> Hi Uko, >> >> If I understand your need correctly, I would say yes : you can add a spec repository: anUrl inside the version and this should override the repository inside the baseline method. >> >> If you're ready to try some of the new stuff pushed in Metacello by Dale, I would suggest that you create a BaselineOfYourProject inside your branch and write a configuration which refer to the baseline; there, just changing the url to point to your branch would make it work. >> >> inside the version method, for example: (gitfiletree url) >> >> spec >> blessing: #development; >> author: 'ThierryGoubier'; >> baseline: 'AltBrowser' >> with: [ spec repository: 'gitfiletree://github.com/ThierryGoubier/AltBrowser.git?branch=pharo4.0 <http://github.com/ThierryGoubier/AltBrowser.git?branch=pharo4.0>' ]; >> import: 'AltBrowser' >> >> (It's also quite convenient to be able to work with metacello scripts which are as short as loading the configuration in the first place: >> >> Metacello new >> baseline: 'AltBrowser'; >> repository: 'gitfiletree://github.com/ThierryGoubier/AltBrowser:pharo4.0 <http://github.com/ThierryGoubier/AltBrowser:pharo4.0>'; >> load >> >> And you can then customize your dependencies per branches, by modifying the BaselineOf in each. >> >> Thierry >> >> >> 2015-02-01 16:21 GMT+01:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: >> Hi, >> >> Iâm using git for versioning, and usually I just work with master branch. Now I have created another branch, can I create at least temporal symbolic version that will work on a current baseline, but will use different ârepositoryâ and so other branch? Or is there another good way to handle branches? >> >> Uko >> > >

Feb. 3, 2015

Re: [Pharo-dev] can a Float be not finite and not equals to Float class>>#infinity ?

by Esteban Lorenzano

yeah :( > On 03 Feb 2015, at 17:02, Chris Cunningham <cunningham.cb(a)gmail.com> wrote: > > Ah, there is also NaN (not a number). > > So, float can be: > NegativeInfinity > a Finite Float > Infinity (;positive by elimination) > NaN > > Oh, and NegativeZero as well. > > floats are weird. > > -cbc > > On Tue, Feb 3, 2015 at 7:51 AM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > in fact, I wonder why #isFinite is implemented: > > ^(self - self) = 0.0 > > and not just: > > ^self isInfinite not > > which includes the negativeInfinityâ¦ > > Esteban > > >> On 03 Feb 2015, at 16:46, Chris Cunningham <cunningham.cb(a)gmail.com <mailto:cunningham.cb@gmail.com>> wrote: >> >> There is Float infinity and Float negativeInfinity - two infinite classes. >> >> Can I assume your first test really wanted to be: >> >> aFloat isFinite = false >> ? >> >> cbc >> >> On Tue, Feb 3, 2015 at 7:38 AM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >> Hi, >> >> thatâ¦ I wonder if >> >> aFloat isFinite = true >> >> and >> >> (aFloat == Float infinite) = false >> >> is a possible combination >> >> Esteban >> > >

Feb. 3, 2015