- Pharo-dev - lists.pharo.org

Re: [Pharo-project] SSL plugin for linux

by Esteban Lorenzano

... and I updated zinc and zodiac (versions were old) and tests are green again. Is that correct? On May 1, 2012, at 6:51 PM, Sven Van Caekenberghe wrote: > > On 01 May 2012, at 17:59, Esteban Lorenzano wrote: > >> I have a version of SSL working on cocoa build, with all Zodiac test passing... I need to check something else? > > You should load the Zinc-Zodiac package for its HTTPS tests. > > The problems with the Mac OS X plugin are related to certificates: they are ignored in Zdc because they don't work. Which also makes it impossible to run an HTTPS server. > > But a working build is the first step. > > Sven > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > > > >

May 1, 2012

Re: [Pharo-project] SSL plugin for linux

by Esteban Lorenzano

ok... now I have failing tests :) On May 1, 2012, at 6:51 PM, Sven Van Caekenberghe wrote: > > On 01 May 2012, at 17:59, Esteban Lorenzano wrote: > >> I have a version of SSL working on cocoa build, with all Zodiac test passing... I need to check something else? > > You should load the Zinc-Zodiac package for its HTTPS tests. > > The problems with the Mac OS X plugin are related to certificates: they are ignored in Zdc because they don't work. Which also makes it impossible to run an HTTPS server. > > But a working build is the first step. > > Sven > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > > > >

May 1, 2012

[Pharo-project] [update 2.0] #20035

by Marcus Denker

20035 ----- Issue 5762: Some initialization fixes in WeakFinalizationList http://code.google.com/p/pharo/issues/detail?id=5762 Issue 5761: Some initialization fixes in FileDirectory http://code.google.com/p/pharo/issues/detail?id=5761 Issue 5759: Some initialization fixes in Graphics-External-Ffenestri http://code.google.com/p/pharo/issues/detail?id=5759 Issue 5746: Add announcer property into morph http://code.google.com/p/pharo/issues/detail?id=5746 -- Marcus Denker -- http://marcusdenker.de

May 1, 2012

Re: [Pharo-project] SSL plugin for linux

by Sean P. DeNigris

Sven Van Caekenberghe wrote > > The problems with the Mac OS X plugin are related to certificates > What is the problem exactly? I remember Ruby had a problem with Mac certificates... maybe we can adapt it... Sven Van Caekenberghe wrote > > they are ignored in Zdc because they don't work > Is that dangerous? -- View this message in context: http://forum.world.st/SSL-plugin-for-linux-tp4593285p4601169.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 1, 2012

[Pharo-project] Pharo 2.0: Just need a recompileAll or a real problem in background?

by Mariano Martinez Peck

(Smalltalk globals associationAt: #ScriptLoader) == ((SmalltalkImage >> #shrinkToCore) literalAt: 4) gives false when it should be true. If I do a Compiler recompileAll it gets fixed. So, my question is, is that normal? how could that happen? is there any real problem behind? anyway, can we do a recompileAll for the moment? thanks! -- Mariano http://marianopeck.wordpress.com

May 1, 2012

Re: [Pharo-project] SSL plugin for linux

by Sven Van Caekenberghe

On 01 May 2012, at 17:59, Esteban Lorenzano wrote: > I have a version of SSL working on cocoa build, with all Zodiac test passing... I need to check something else? You should load the Zinc-Zodiac package for its HTTPS tests. The problems with the Mac OS X plugin are related to certificates: they are ignored in Zdc because they don't work. Which also makes it impossible to run an HTTPS server. But a working build is the first step. Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

May 1, 2012

Re: [Pharo-project] problem with tempNamed: in Pharo 2.0

by Mariano Martinez Peck

On Tue, May 1, 2012 at 6:09 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > Hi guys. I noticed stef did this issue: > http://code.google.com/p/pharo/issues/detail?id=5642 > However, now I have the following test that fails in Pharo 2.0 but works > fine in 1.4: > > | string context | > string := 'test'. > context := [self class. string asUppercase] asContext. > self assert: (context tempNamed: 'string') = 'test' > > the current implementation of #tempNamed: is: > > tempNamed: aName > "Returns the value of the temporaries, aName." > "Implementation notes: temporary initialization in blocks simply uses > pushNil to allocate and initialize each temp. So if one inspects [|a|a:=2] > and sends it self method symbolic you get: > > 13 <8F 00 00 05> closureNumCopied: 0 numArgs: 0 bytes 17 to 21 > 17 <73> pushConstant: nil > 18 <77> pushConstant: 2 > 19 <81 40> storeIntoTemp: 0 > 21 <7D> blockReturn > 22 <7C> returnTop > > And when we check self asContext pc we get 17, which is *before* the > nil is pushed. Therefore we should pay attention when querying a temporary > if the temporary allocation was executed." > > | index | > index := (self tempNames indexOf: aName). > ^ index >= stackp > Maybe the solution is to use #> rather than #>= ? > ifTrue: [ nil] > ifFalse: [self tempAt: (self tempNames indexOf: aName)] > > > and previously it was: > > tempNamed: aName > ^self tempAt: (self tempNames indexOf: aName) > > > ideas? > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

May 1, 2012

[Pharo-project] problem with tempNamed: in Pharo 2.0

by Mariano Martinez Peck

Hi guys. I noticed stef did this issue: http://code.google.com/p/pharo/issues/detail?id=5642 However, now I have the following test that fails in Pharo 2.0 but works fine in 1.4: | string context | string := 'test'. context := [self class. string asUppercase] asContext. self assert: (context tempNamed: 'string') = 'test' the current implementation of #tempNamed: is: tempNamed: aName "Returns the value of the temporaries, aName." "Implementation notes: temporary initialization in blocks simply uses pushNil to allocate and initialize each temp. So if one inspects [|a|a:=2] and sends it self method symbolic you get: 13 <8F 00 00 05> closureNumCopied: 0 numArgs: 0 bytes 17 to 21 17 <73> pushConstant: nil 18 <77> pushConstant: 2 19 <81 40> storeIntoTemp: 0 21 <7D> blockReturn 22 <7C> returnTop And when we check self asContext pc we get 17, which is *before* the nil is pushed. Therefore we should pay attention when querying a temporary if the temporary allocation was executed." | index | index := (self tempNames indexOf: aName). ^ index >= stackp ifTrue: [ nil] ifFalse: [self tempAt: (self tempNames indexOf: aName)] and previously it was: tempNamed: aName ^self tempAt: (self tempNames indexOf: aName) ideas? -- Mariano http://marianopeck.wordpress.com

May 1, 2012

Re: [Pharo-project] SSL plugin for linux

by Esteban Lorenzano

On May 1, 2012, at 6:02 PM, Sean P. DeNigris wrote: > > EstebanLM wrote >> >> I have a version of SSL working on cocoa build, with all Zodiac test >> passing > > Wow, that was quick! he... it was quite easy in fact... that's why I'm suspicious about the result, and I want to check it better :)

May 1, 2012

Re: [Pharo-project] SSL plugin for linux

by Sean P. DeNigris

EstebanLM wrote > > I have a version of SSL working on cocoa build, with all Zodiac test > passing Wow, that was quick! -- View this message in context: http://forum.world.st/SSL-plugin-for-linux-tp4593285p4601045.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 1, 2012