March 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Path>>/ and ..

by Esteban Lorenzano

Hi, problem is this part: '../eâ it has to be any of this: ('/a/b/c/d' asFileReference / '..' / 'e') path. "Path / 'a' / 'b' / 'c' / 'd' / '..' / 'e'" ('/a/b/c/d' asFileReference parent / 'e') path. "Path / 'a' / 'b' / 'c' / 'e'" the rationale is that â..â is not modelled as a special kind of node, just a string. and the reason is that thatâs commonly like that, but it doesnât *has to* be like thatâ¦ there could be file systems that interprets .. as a simple string. and everything can be improved :) Esteban > On 29 Mar 2017, at 12:21, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi All, > > The current implementation of Path>>/, while functional, seems to me to > create poorly formed paths, e.g.: > > ('/a/b/c/d' asFileReference / '../e') path ==> "Path / 'a' / 'b' / 'c' > / 'd' / '../e'" > > As can be seen above, the last segment is '../e'. > > I would expect the result to be: > > "Path / 'a' / 'b' / 'c' / 'e'" > > Is there a reason for the current behaviour? If not, are people open to > modifying Path>>/ to produce the suggested result above (in Pharo 7)? > > The method below produces the modified result above and doesn't change > the result of running all automated tests. If this is going to be added > to Pharo 7 I'll create an additional automated test to check that it is > working properly. > > Cheers, > Alistair > > 'From Pharo6.0 of 13 May 2016 [Latest update: #60451] on 29 March 2017 > at 9:40:41.681228 am'! > > !Path methodsFor: 'navigating' stamp: 'AlistairGrant 3/29/2017 09:39'! > / aString > | path | > > aString isEmptyOrNil > ifTrue: [ Error signal: 'Path element cannot be empty or nil']. > > ^self resolve: (Path from: aString) > ! ! >

March 29, 2017

Re: [Pharo-dev] the new "fixed" compactor VM has FT broken...

by Esteban Lorenzano

> On 29 Mar 2017, at 12:39, Stan Krupoderov <pashelper(a)gmail.com> wrote: > > Hi Esteban, > > > we moved the paradigm a couple of years ago: each Pharo version comes with his own VM version > Thanks for clarification. I see your point. Will it be always the same way or it should be changed once VM and Pharo 6 are stabilized? always like that, is the idea. > > How update scenario should be handled in this case on the user side? > Will it be File-out and File-in for all user changes? you save your project, then you load itâ¦ as always. 99% of things should work without any problem. > > And unfortunately this doesn't add clarity on why Pharo 5 is so unstable out of the box and if > there any plans to fix existing issues in Pharo 5. Do you have any thoughts on this matter? > Can we help with this? Pharo 5 is not unstable. There is however a problem with Athens and UFFI in Pharo5 that makes that part unstable. There was also a FT2 (important) problem but it was fixed. Anyway, this Athens problems are very hard to fix and we preview to fix that in Pharo 6, not in Pharo 5. Pharo 6 is two/three weeks of release, btw. Esteban > > On Wed, Mar 29, 2017 at 1:05 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > > > On 29 Mar 2017, at 11:39, Peter Uhnak <i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>> wrote: > > > > On Wed, Mar 29, 2017 at 11:05:28AM +0200, Esteban Lorenzano wrote: > >> wellâ¦ > >> > >> Latest VM is intended to work with latest Pharo, not with older versions. > >> Latest VM is *always* an experimental/unstable VM that needs to be consideredâ¦ that, experimental and unstable. Otherwise there would not be point on having the distinction between stable/latest, isnât? > >> > > > >> So, no, Latest VM (which can also be known as âalpha vmâ) has not broken FT, it works fine in Pharo 6.0, which can also be know as âPharo 6.0 Alphaâ). > >> > >> BTWâ¦ Thatâs why in zeroconf you cannot download a âlatest vm for Pharo 5â. > >> > >> Of course, you can live at the edge, but that doesnât means something is broken when something fails if premises are not fulfilled :) > > > > Well considering VM for Pharo 5 never worked for me properly, whether it was crashing on BitBlt/Cairo, FT, or who knows what, I don't really have a choice but to use the latest. If there is a better way then I am all ears, constantly dealing with crashing VM when I need to get work done is extremely frustrating... > > > > Also I was under the impression that newer VM should work with older images, with the only exception being Cog/Spur change. Or should I have six different VMs and Pharo Launcher with six different VM configurations? > > we moved the paradigm a couple of years ago: each Pharo version comes with his own VM version (Other smalltalks do that too). > Being infinite backward compatible is a lot of pain :) > > so yes, PharoLauncher needs to adapt to itâ¦ I added that requirement for PharoLauncher: you ship with latest stable but you can always download newers or olders (this is not yet implemented, is just a requirement I addedâ¦ well, couple of years ago when we changed the way we wanted VMs to work). > > Esteban > > > > > Peter > > > >> > >> Said thatâ¦ I had no problems with Latest VM + Pharo 6.0 (and they may happen, since this is all alfa :P) > >> > >> I donât know if âworkarounding the VMâ (by renaming libfreetype) will work, but if that works, ONCE we move latest vm to stable status we can consider backporting it to Pharo 5. > >> > >> Esteban > >> > >>> On 29 Mar 2017, at 10:37, Peter Uhnak <i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>> wrote: > >>> > >>> The new "fixed" compactor VM has broken FT... > >>> > >>> So any text drawn on Athens canvas results in red cross... > >>> > >>> Error in... > >>> > >>> CairoFontFace class>>primFtFace:loadFlags: > >>> > >>> 'Unable to find function address' > >>> > >>> Apparently because someone renamed libfreetype-6.dll to libfreetype.dll > >>> > >>> (Windows VM latest, Pharo 5) > >>> > >> > >> > > > > > > > > -- > Regards, > Stanislav S. Krupoderov

March 29, 2017

NumberParser and exponent

by Henrik Nergaard

Hi, Apperently the number parser cannot parse '2E+2' correctly, is this a bug or a feature. ('2E+2' asNumber = '2e2' asNumber) Is there any reason to why parsing numbers with uppercase exponent letter is not allowed? (see NumberParser >> #exponentLetters) The parser has a method named #allowPlusSignInExponent sending self >> #allowPlusSign which just returns false. Is there any reason for not allowing the pluss sign / having it as true instead? (I guess it should at least be an ivar so it can be configured?). Best regards, Henrik

March 29, 2017

Re: [Pharo-dev] the new "fixed" compactor VM has FT broken...

by Stan Krupoderov

Hi Esteban, > we moved the paradigm a couple of years ago: each Pharo version comes with his own VM version Thanks for clarification. I see your point. Will it be always the same way or it should be changed once VM and Pharo 6 are stabilized? How update scenario should be handled in this case on the user side? Will it be File-out and File-in for all user changes? And unfortunately this doesn't add clarity on why Pharo 5 is so unstable out of the box and if there any plans to fix existing issues in Pharo 5. Do you have any thoughts on this matter? Can we help with this? On Wed, Mar 29, 2017 at 1:05 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > On 29 Mar 2017, at 11:39, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > > > On Wed, Mar 29, 2017 at 11:05:28AM +0200, Esteban Lorenzano wrote: > >> wellâ¦ > >> > >> Latest VM is intended to work with latest Pharo, not with older > versions. > >> Latest VM is *always* an experimental/unstable VM that needs to be > consideredâ¦ that, experimental and unstable. Otherwise there would not be > point on having the distinction between stable/latest, isnât? > >> > > > >> So, no, Latest VM (which can also be known as âalpha vmâ) has not > broken FT, it works fine in Pharo 6.0, which can also be know as âPharo 6.0 > Alphaâ). > >> > >> BTWâ¦ Thatâs why in zeroconf you cannot download a âlatest vm for Pharo > 5â. > >> > >> Of course, you can live at the edge, but that doesnât means something > is broken when something fails if premises are not fulfilled :) > > > > Well considering VM for Pharo 5 never worked for me properly, whether it > was crashing on BitBlt/Cairo, FT, or who knows what, I don't really have a > choice but to use the latest. If there is a better way then I am all ears, > constantly dealing with crashing VM when I need to get work done is > extremely frustrating... > > > > Also I was under the impression that newer VM should work with older > images, with the only exception being Cog/Spur change. Or should I have six > different VMs and Pharo Launcher with six different VM configurations? > > we moved the paradigm a couple of years ago: each Pharo version comes with > his own VM version (Other smalltalks do that too). > Being infinite backward compatible is a lot of pain :) > > so yes, PharoLauncher needs to adapt to itâ¦ I added that requirement for > PharoLauncher: you ship with latest stable but you can always download > newers or olders (this is not yet implemented, is just a requirement I > addedâ¦ well, couple of years ago when we changed the way we wanted VMs to > work). > > Esteban > > > > > Peter > > > >> > >> Said thatâ¦ I had no problems with Latest VM + Pharo 6.0 (and they may > happen, since this is all alfa :P) > >> > >> I donât know if âworkarounding the VMâ (by renaming libfreetype) will > work, but if that works, ONCE we move latest vm to stable status we can > consider backporting it to Pharo 5. > >> > >> Esteban > >> > >>> On 29 Mar 2017, at 10:37, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > >>> > >>> The new "fixed" compactor VM has broken FT... > >>> > >>> So any text drawn on Athens canvas results in red cross... > >>> > >>> Error in... > >>> > >>> CairoFontFace class>>primFtFace:loadFlags: > >>> > >>> 'Unable to find function address' > >>> > >>> Apparently because someone renamed libfreetype-6.dll to libfreetype.dll > >>> > >>> (Windows VM latest, Pharo 5) > >>> > >> > >> > > > > > -- Regards, Stanislav S. Krupoderov

March 29, 2017

Path>>/ and ..

by Alistair Grant

Hi All, The current implementation of Path>>/, while functional, seems to me to create poorly formed paths, e.g.: ('/a/b/c/d' asFileReference / '../e') path ==> "Path / 'a' / 'b' / 'c' / 'd' / '../e'" As can be seen above, the last segment is '../e'. I would expect the result to be: "Path / 'a' / 'b' / 'c' / 'e'" Is there a reason for the current behaviour? If not, are people open to modifying Path>>/ to produce the suggested result above (in Pharo 7)? The method below produces the modified result above and doesn't change the result of running all automated tests. If this is going to be added to Pharo 7 I'll create an additional automated test to check that it is working properly. Cheers, Alistair 'From Pharo6.0 of 13 May 2016 [Latest update: #60451] on 29 March 2017 at 9:40:41.681228 am'! !Path methodsFor: 'navigating' stamp: 'AlistairGrant 3/29/2017 09:39'! / aString | path | aString isEmptyOrNil ifTrue: [ Error signal: 'Path element cannot be empty or nil']. ^self resolve: (Path from: aString) ! !

March 29, 2017

Re: [Pharo-dev] the new "fixed" compactor VM has FT broken...

by Esteban Lorenzano

> On 29 Mar 2017, at 11:39, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > On Wed, Mar 29, 2017 at 11:05:28AM +0200, Esteban Lorenzano wrote: >> wellâ¦ >> >> Latest VM is intended to work with latest Pharo, not with older versions. >> Latest VM is *always* an experimental/unstable VM that needs to be consideredâ¦ that, experimental and unstable. Otherwise there would not be point on having the distinction between stable/latest, isnât? >> > >> So, no, Latest VM (which can also be known as âalpha vmâ) has not broken FT, it works fine in Pharo 6.0, which can also be know as âPharo 6.0 Alphaâ). >> >> BTWâ¦ Thatâs why in zeroconf you cannot download a âlatest vm for Pharo 5â. >> >> Of course, you can live at the edge, but that doesnât means something is broken when something fails if premises are not fulfilled :) > > Well considering VM for Pharo 5 never worked for me properly, whether it was crashing on BitBlt/Cairo, FT, or who knows what, I don't really have a choice but to use the latest. If there is a better way then I am all ears, constantly dealing with crashing VM when I need to get work done is extremely frustrating... > > Also I was under the impression that newer VM should work with older images, with the only exception being Cog/Spur change. Or should I have six different VMs and Pharo Launcher with six different VM configurations? we moved the paradigm a couple of years ago: each Pharo version comes with his own VM version (Other smalltalks do that too). Being infinite backward compatible is a lot of pain :) so yes, PharoLauncher needs to adapt to itâ¦ I added that requirement for PharoLauncher: you ship with latest stable but you can always download newers or olders (this is not yet implemented, is just a requirement I addedâ¦ well, couple of years ago when we changed the way we wanted VMs to work). Esteban > > Peter > >> >> Said thatâ¦ I had no problems with Latest VM + Pharo 6.0 (and they may happen, since this is all alfa :P) >> >> I donât know if âworkarounding the VMâ (by renaming libfreetype) will work, but if that works, ONCE we move latest vm to stable status we can consider backporting it to Pharo 5. >> >> Esteban >> >>> On 29 Mar 2017, at 10:37, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >>> >>> The new "fixed" compactor VM has broken FT... >>> >>> So any text drawn on Athens canvas results in red cross... >>> >>> Error in... >>> >>> CairoFontFace class>>primFtFace:loadFlags: >>> >>> 'Unable to find function address' >>> >>> Apparently because someone renamed libfreetype-6.dll to libfreetype.dll >>> >>> (Windows VM latest, Pharo 5) >>> >> >> >

March 29, 2017

Re: [Pharo-dev] the new "fixed" compactor VM has FT broken...

by Peter Uhnak

On Wed, Mar 29, 2017 at 11:05:28AM +0200, Esteban Lorenzano wrote: > wellâ¦ > > Latest VM is intended to work with latest Pharo, not with older versions. > Latest VM is *always* an experimental/unstable VM that needs to be consideredâ¦ that, experimental and unstable. Otherwise there would not be point on having the distinction between stable/latest, isnât? > > So, no, Latest VM (which can also be known as âalpha vmâ) has not broken FT, it works fine in Pharo 6.0, which can also be know as âPharo 6.0 Alphaâ). > > BTWâ¦ Thatâs why in zeroconf you cannot download a âlatest vm for Pharo 5â. > > Of course, you can live at the edge, but that doesnât means something is broken when something fails if premises are not fulfilled :) Well considering VM for Pharo 5 never worked for me properly, whether it was crashing on BitBlt/Cairo, FT, or who knows what, I don't really have a choice but to use the latest. If there is a better way then I am all ears, constantly dealing with crashing VM when I need to get work done is extremely frustrating... Also I was under the impression that newer VM should work with older images, with the only exception being Cog/Spur change. Or should I have six different VMs and Pharo Launcher with six different VM configurations? Peter > > Said thatâ¦ I had no problems with Latest VM + Pharo 6.0 (and they may happen, since this is all alfa :P) > > I donât know if âworkarounding the VMâ (by renaming libfreetype) will work, but if that works, ONCE we move latest vm to stable status we can consider backporting it to Pharo 5. > > Esteban > > > On 29 Mar 2017, at 10:37, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > > > The new "fixed" compactor VM has broken FT... > > > > So any text drawn on Athens canvas results in red cross... > > > > Error in... > > > > CairoFontFace class>>primFtFace:loadFlags: > > > > 'Unable to find function address' > > > > Apparently because someone renamed libfreetype-6.dll to libfreetype.dll > > > > (Windows VM latest, Pharo 5) > > > >

March 29, 2017

Re: [Pharo-dev] the new "fixed" compactor VM has FT broken...

by Esteban Lorenzano

wellâ¦ Latest VM is intended to work with latest Pharo, not with older versions. Latest VM is *always* an experimental/unstable VM that needs to be consideredâ¦ that, experimental and unstable. Otherwise there would not be point on having the distinction between stable/latest, isnât? So, no, Latest VM (which can also be known as âalpha vmâ) has not broken FT, it works fine in Pharo 6.0, which can also be know as âPharo 6.0 Alphaâ). BTWâ¦ Thatâs why in zeroconf you cannot download a âlatest vm for Pharo 5â. Of course, you can live at the edge, but that doesnât means something is broken when something fails if premises are not fulfilled :) Said thatâ¦ I had no problems with Latest VM + Pharo 6.0 (and they may happen, since this is all alfa :P) I donât know if âworkarounding the VMâ (by renaming libfreetype) will work, but if that works, ONCE we move latest vm to stable status we can consider backporting it to Pharo 5. Esteban > On 29 Mar 2017, at 10:37, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > The new "fixed" compactor VM has broken FT... > > So any text drawn on Athens canvas results in red cross... > > Error in... > > CairoFontFace class>>primFtFace:loadFlags: > > 'Unable to find function address' > > Apparently because someone renamed libfreetype-6.dll to libfreetype.dll > > (Windows VM latest, Pharo 5) >

March 29, 2017

Re: [Pharo-dev] debugger inspector pane different than inspect pane?

by Andrei Chis

Not aware of this bug. I tried to debug a few other objects that have custom tree presentations and they seem to work. I'll need a way to reproduce this. Can you paste the code of the custom presentation that is problematic. Cheers, Andrei On Wed, Mar 29, 2017 at 9:11 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi andrei > > I'm debugger a node of a tree and in the debugger > the tree pane is empty. Now when I click on the node and inspect > it I get a tree representation. > > I do not know if you are aware of this behavior. > > Stef >

March 29, 2017

the new "fixed" compactor VM has FT broken...

by Peter Uhnak

The new "fixed" compactor VM has broken FT... So any text drawn on Athens canvas results in red cross... Error in... CairoFontFace class>>primFtFace:loadFlags: 'Unable to find function address' Apparently because someone renamed libfreetype-6.dll to libfreetype.dll (Windows VM latest, Pharo 5)

March 29, 2017