- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Fuel

by Guillermo Polito

Steph wants less hardcoded references to PackageInfo :) On Wed, Jun 6, 2012 at 10:51 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > Hmm I didn't catch it > > Martin > > On Wed, Jun 6, 2012 at 4:47 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > > ok for me > > I'm studying PackageInfo and the rest to see what I can do. > > > >> mariano/martin > >> > >> I would like to extract PakageInfo into self packageInfo in the > fuel code. > >> > >> Yes, I like that the idea. I guess you are talking about > FuelPackageLoader in #named: and #withPacakges: right? > >> What about calling it direclty #package? so that we may be able to > change it later to PackageInfo or RPackage or whatever? > >> > >> > >> Can I do it? > >> > >> Stef > >> > >> > >> > >> > >> -- > >> Mariano > >> http://marianopeck.wordpress.com > >> > > > > > >

June 6, 2012

Re: [Pharo-project] Fuel

by Martin Dias

Hmm I didn't catch it Martin On Wed, Jun 6, 2012 at 4:47 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > ok for me > I'm studying PackageInfo and the rest to see what I can do. > >> mariano/martin >> >> Â Â Â Â I would like to extract PakageInfo into self packageInfo in the fuel code. >> >> Yes, I like that the idea. I guess you are talking about FuelPackageLoader in #named: and #withPacakges: right? >> What about calling it direclty #package? Â so that we may be able to change it later to PackageInfo or RPackage or whatever? >> >> >> Can I do it? >> >> Stef >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > >

June 6, 2012

Re: [Pharo-project] FilePlugin changed it's behavior?

by StÃ©phane Ducasse

> is not failing as it says it should in the comment. > > Has this behavior changed lately? Should this be fixed in the vm side, wait for NativeBoost? Or we should just by now fix the comment and clients not to expect that? I think that we should put all our eggs in the same basket :) so the non native boost version should work too. > some pointer? > > Tx

June 6, 2012

Re: [Pharo-project] Fuel

by StÃ©phane Ducasse

ok for me I'm studying PackageInfo and the rest to see what I can do. > mariano/martin > > I would like to extract PakageInfo into self packageInfo in the fuel code. > > Yes, I like that the idea. I guess you are talking about FuelPackageLoader in #named: and #withPacakges: right? > What about calling it direclty #package? so that we may be able to change it later to PackageInfo or RPackage or whatever? > > > Can I do it? > > Stef > > > > > -- > Mariano > http://marianopeck.wordpress.com >

June 6, 2012

Re: [Pharo-project] Something does not work with issue tracker status

by phil＠highoctane.be

Why not organize "feature teams" along packages or package sets on which experts have approval power? Of course, some stuff will be cross packages but still, it should work. Is there any chart or trend in there, like bugs unfixed since x days that should be? Phil 2012/6/6 Sean P. DeNigris <sean(a)clipperadams.com> > > Mariano Martinez Peck wrote > > > > We really need people helping review changes... So, please, help us > review > > issues. Is the only way > > to improve. > > > > +1. I will try a few... > > Sean > > -- > View this message in context: > http://forum.world.st/Something-does-not-work-with-issue-tracker-status-tp4… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Philippe Back "Helping you hit the top 3 outcomes you really want to achieve" Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be| Web: http://philippeback.eu | Blog: http://philippeback.be High Octane SPRL rue cour Boisacq 101 1301 Bierges

June 6, 2012

Re: [Pharo-project] Something does not work with issue tracker status

by Sean P. DeNigris

Mariano Martinez Peck wrote > > We really need people helping review changes... So, please, help us review > issues. Is the only way > to improve. > +1. I will try a few... Sean -- View this message in context: http://forum.world.st/Something-does-not-work-with-issue-tracker-status-tp4… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 6, 2012

[Pharo-project] FilePlugin changed it's behavior?

by Guillermo Polito

Hi guys, I'm looking at this issue: http://code.google.com/p/pharo/issues/detail?can=2&start=0&num=100&q=&colsp… . And debugging, it seems that the primitive rename: oldFileFullName to: newFileFullName "Rename the file of the given name to the new name. Fail if there is no file of the old name or if there is an existing file with the new name." <primitive: 'primitiveFileRename' module: 'FilePlugin'> ^nil is not failing as it says it should in the comment. Has this behavior changed lately? Should this be fixed in the vm side, wait for NativeBoost? Or we should just by now fix the comment and clients not to expect that? some pointer? Tx

June 6, 2012

[Pharo-project] Something does not work with issue tracker status

by Mariano Martinez Peck

Hi guys. Previously, we use to mark issues as "Fixed" once someone proposed a solution. Now we have to first put it as ""FixReviewNeeded" and then when someone else takes the time to review it put it as "FixToInclude". Now...the problem is that nobody reviews and issues get outdated. And then, when trying to load the slice or .cs it does not work anyomre, or it is outdated, or whatever. Meaning that it has to be regenerated and we spend the double of time. So, what can we do to improve this???? ideas: 1) We should be more confident ourselves. Imagine we have proposed something and it is as "FixReviewNeeded". If we have run the tests, and we didn't break anything, and the problem is really fixed, and the topic is not something REALLY critical, and no one has reviewed your issue, why not to putting it as "FixToInclude" ? 2) We really need people helping review changes. There are only a few guys that do this. You DON'T need to be an expert. "FixReviewNeeded" does not mean "HasToBeReviewedByAGuruExperiencedHacker". It just means "it just requires another eyes". So, please, help us review issues. Is the only way to improve. so, what do you think? -- Mariano http://marianopeck.wordpress.com

June 6, 2012

Re: [Pharo-project] Fuel

by Mariano Martinez Peck

On Wed, Jun 6, 2012 at 5:39 PM, stephane ducasse <stephane.ducasse(a)free.fr>wrote: > mariano/martin > > I would like to extract PakageInfo into self packageInfo in the > fuel code. > Yes, I like that the idea. I guess you are talking about FuelPackageLoader in #named: and #withPacakges: right? What about calling it direclty #package? so that we may be able to change it later to PackageInfo or RPackage or whatever? > > Can I do it? > > Stef > > -- Mariano http://marianopeck.wordpress.com

June 6, 2012

[Pharo-project] Fuel

by stephane ducasse

mariano/martin I would like to extract PakageInfo into self packageInfo in the fuel code. Can I do it? Stef

June 6, 2012