January 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Generating ticket (was Re: Generators for Pharo Xmax wish))

by StÃ©phane Ducasse

Ralph go on code.google.com/p/pharo then select issue: then create a new one. Stef On Jan 9, 2011, at 7:37 PM, Ralph Boland wrote: >> The easiest way to get this code into pharo core is to create a mcz >> package, put it on PharoInbox on squeaksource and create a ticket in >> code.google.com/p/pharo referencing it and taggint it Fixed, this way >> St?phane or Markus can harvest it to the core image. > > I am clear on how to do this (I am not a Pharo user). > I went to: > code.google.com/p/pharo > and from there I went to > squeaksource.com/PharoInbox/feed.rss > and subscribed. But I don't see how to add any text to the site. > I assume that "ticket" is a bug report but I don't know how to generate > one for Pharo. > > Please send instructions on how to do the above. > > >> If the mcz package is overkill, then a simple fileout of the package in >> squeak attached to the ticket will do. > >> Maybe in the long term a project on squeaksource should be created (if >> not exists) and new changes to to it and from there pulled to squeak and >> pharo. > > I believe Andreas Raab originally created a project for generators on > squeaksource but it doesn't appear to be there now. Perhaps it was > removed once the generators package was incorporated into Squeak. > > > Ralph Boland >

Jan. 9, 2011

Re: [Pharo-project] Pharo sprint @ lille Friday 21 of January

by StÃ©phane Ducasse

pass the message around you that people should reply here so that we know which organization to set up. On Jan 9, 2011, at 7:07 PM, Benjamin Van Ryseghem wrote: > I'll be there ^^ > > > Ben > > 2011/1/9 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Hi guys > > we will have a pharo sprint at Lille Friday 21 of January. If you want to join let us know that we organize for the food. > The sprint will happen in our rooms at LIFL > http://rmod.lille.inria.fr/web/pier/contactr/ > > Stef >

Jan. 9, 2011

Re: [Pharo-project] [squeak-dev] Re: [Seaside-dev] Seaside and exception behaviour

by Julian Fitzell

Hi Andreas, A neat approach, but I don't think it quite works (yet, anyway). Although it has the correct behaviour when the exception action is invoked, it doesn't behave correctly for #defaultAction. According to 5.5.2.1 in the spec, "The #defaultAction method is executed in the context of the signaling environment." So, taking an example of an existing #defaultAction method that signals an exception: [ Error signal ] on: UnhandledError do: [ :ex | 'ANSI says so' ] returns 'ANSI says so' without your change but brings up a debugger with it. Julian On Sat, Jan 8, 2011 at 7:34 PM, Andreas Raab <andreas.raab(a)gmx.de> wrote: > Thanks for the test case. I've posted a possible fix for Squeak to the inbox > (Kernel-ar.540) but I'd like people to review the change first since it's a > fairly critical part of the system. I'd appreciate if someone could look at > the fix and comment on whether that's the sensible thing to do. > > Cheers, > Â - Andreas > > On 1/8/2011 6:02 PM, Julian Fitzell wrote: >> >> On Wed, Jan 5, 2011 at 8:15 AM, Paolo Bonzini<bonzini(a)gnu.org> Â wrote: >>> >>> On 01/05/2011 04:58 PM, mkobetic(a)cincom.com wrote: >>>> >>>>>> Â Here's maybe a bit more concise example. If you run the thing below >>>>>> in a workspace, >>>>>> Â it returns 'Squeak' in Squeak and 'VW' in VW >>>>>> >>>>>> Â [ Â [ Â Â Â [ Â Â Â self error: 'trigger error' >>>>>> Â Â Â Â Â Â ] on: ZeroDivide do: [ :ex | 'Squeak' ] >>>>>> Â Â ] on: Error do: [ :ex | 3 / 0 ] >>>>>> Â ] on: ZeroDivide do: [ :ex | 'VW' ] >>>>> >>>>> Â It returns 'Squeak' on GNU Smalltalk. Â This is consistent with my >>>>> Â analysis of Alan's snippet. Â Unfortunately I don't have at hand my >>>>> copy >>>>> Â of the standard. >>>> >>>> FWIW, Smalltalk/X returns 'VW' >>> >>> That's the correct behavior. Â The standard says the search should proceed >>> from the last exception handler that was created up to the oldest. >> >> Agreed. Â The ANSI standard seems quite clear about that: >> >> 5.4.3.3: "If signaling of an exception results in evaluation of action >> the evaluation will occur in the context of the handler environment." >> >> 5.5.2.1: "If a matching handler is found, the exception action of the >> handler is evaluated in the exception environment that was current >> when the handler was created and the state of the current exception >> environment is preserved as the signaling environment." >> >>> (That said, Squeak/gst's behavior is quite easy to justify, as stack >>> unwinding hasn't happened yet. Â I'll wait for this thread to settle >>> before >>> changing it in gst). >> >> But stack unwinding shouldn't need to happen until one of the #on:do: >> calls is actually ready to return. Until then, its all just searching. >> >> I think Squeak/Pharo's problem is that it doesn't maintain a first >> class "exception environment" as described by the glossary in the ANSI >> standard: "An abstract entity that is a LIFO list of exception >> handlers. An exception environment may be logically searched starting >> from the most recently "pushed" exception handler." >> >> Squeak/Pharo simply (ab)uses the context chain, walking it looking for >> the next handler (see the implementation of #signal, which always >> starts searching from thisContext). This works fine most of the time >> but not when you need to temporarily restore a previous exception >> environment. #handleSignal: does go to the effort of setting a >> handlerContext on the signaled exception before calling the action >> block. This is necessary to implement #pass, #isNested, and so on but >> would also need to be put somewhere that #signal could get at it to >> use as a starting point for the search. >> >> This seems like a squeak/pharo bug to me. I don't much feel like >> fixing it in Grease given that Grease is supposed to assume correct >> ANSI implementation as a pre-requisite. Perhaps we can broker a deal >> where Squeak/Pharo will fix this and VW (finally) fixes its signaling >> behaviour so we can drop GRError, etc. entirely. >> >> In the meantime, though, how would we fix the Seaside code assuming we >> had ANSI-correct exception handling implementations? >> >> Julian >> >> > > >

Jan. 9, 2011

[Pharo-project] Generating ticket (was Re: Generators for Pharo Xmax wish))

by Ralph Boland

> The easiest way to get this code into pharo core is to create a mcz > package, put it on PharoInbox on squeaksource and create a ticket in > code.google.com/p/pharo referencing it and taggint it Fixed, this way > St?phane or Markus can harvest it to the core image. I am clear on how to do this (I am not a Pharo user). I went to: code.google.com/p/pharo and from there I went to squeaksource.com/PharoInbox/feed.rss and subscribed. But I don't see how to add any text to the site. I assume that "ticket" is a bug report but I don't know how to generate one for Pharo. Please send instructions on how to do the above. > If the mcz package is overkill, then a simple fileout of the package in > squeak attached to the ticket will do. > Maybe in the long term a project on squeaksource should be created (if > not exists) and new changes to to it and from there pulled to squeak and > pharo. I believe Andreas Raab originally created a project for generators on squeaksource but it doesn't appear to be there now. Perhaps it was removed once the generators package was incorporated into Squeak. Ralph Boland

Jan. 9, 2011

Re: [Pharo-project] Gofer problem installing packages with the same name

by HernÃ¡n Morales Durand

Hi Lukas, 2011/1/9 Lukas Renggli <renggli(a)gmail.com>: > No, Gofer doesn't look in repositories you don't specify. However, it > uses and prefers your local package-cache if it contains a newer > version of your package (which is likely the case in your example). I see. I assumed that to distinguish a newer version corresponds to the right package, a package included meta-information about its source repositories or some fingerprint. > You can disable the package-cache by sending something like > #disablePackageCache to your Gofer instance (I don't have an image at > hand right now, but you find it in the code and documentation). > Thanks, it worked fine. > Gofer is part of Pharo and not maintained in my repository anymore. > This #update method should be removed it is not supposed to work > anymore. > > Lukas > > On Sunday, 9 January 2011, HernÃ¡n Morales Durand > <hernan.morales(a)gmail.com> wrote: >> Hi list, >> I have some issues with Gofer, maybe already known. When I evaluate: >> >> Gofer new >> Â Â Â Â Â squeaksource: 'Subjectivity'; >> Â Â Â Â Â package: 'Subjectivity'; >> Â Â Â Â Â load. >> >> it seems that Gofer takes the first package named Subjectivity it >> founds which in this case is >> http://www.squeaksource.com/Decisionstrategy.html while I wanted to >> take it from http://www.squeaksource.com/Subjectivity.html (please see >> the screenshot). >> After then I've tried to update "Gofer upgrade" for a fix, but it >> seems it cannot connect to http://source.lukas-renggli.ch and then >> entered in an endless loop. Any hint? >> (Using Pharo1.2beta Latest update: #12294) >> >> Cheers, >> >> -- >> HernÃ¡n Morales >> Information Technology Manager, >> Institute of Veterinary Genetics. >> National Scientific and Technical Research Council (CONICET). >> La Plata (1900), Buenos Aires, Argentina. >> Telephone: +54 (0221) 421-1799. >> Internal: 422 >> Fax: 425-7980 or 421-1799. >> > > -- > Lukas Renggli > www.lukas-renggli.ch >

Jan. 9, 2011

Re: [Pharo-project] Pharo sprint @ lille Friday 21 of January

by Benjamin Van Ryseghem

I'll be there ^^ Ben 2011/1/9 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Hi guys > > we will have a pharo sprint at Lille Friday 21 of January. If you want to > join let us know that we organize for the food. > The sprint will happen in our rooms at LIFL > http://rmod.lille.inria.fr/web/pier/contactr/ > > Stef >

Jan. 9, 2011

Re: [Pharo-project] Issue 3521 in pharo: StringMorphEditor doesn't work

by pharo＠googlecode.com

Updates: Status: Fixed Comment #1 on issue 3521 by aplantec: StringMorphEditor doesn't work http://code.google.com/p/pharo/issues/detail?id=3521 in InBox SLICE-Issue-3521-StringMorphEditor-doesnt-work

Jan. 9, 2011

[Pharo-project] Issue 3521 in pharo: StringMorphEditor doesn't work

by pharo＠googlecode.com

Status: Accepted Owner: aplantec Labels: Milestone-1.2 New issue 3521 by aplantec: StringMorphEditor doesn't work http://code.google.com/p/pharo/issues/detail?id=3521 Used to edit a StringMorph is the 'string morph are editable' is set to true. Do we need that ?

Jan. 9, 2011

[Pharo-project] SqueakSSL Plugin for Mac OS X

by Sven Van Caekenberghe

On 04 Jan 2011, at 18:16, Sven Van Caekenberghe wrote: > Hi, > > Has anyone got the Squeak SSL plugin [1] to work on Mac OS X, more specifically for the Cog VM family, Pharo 1.1.1 or later and Mac OS X 10.6.5 ? If not, is there some how to guide on building plugins ? > > TIA, > > Sven > > [1] http://www.squeaksource.com/SqueakSSL I have found the Google project website for the plugin: http://code.google.com/p/squeakssl/ where binary versions of the plugin can be downloaded for Windows, Mac and Linux. I got this to work in a Cog VM on Mac OS X, however not without at least one problem: SqueakSSL>>#certState always returns -1 on Mac OS X simply because this is hardcoded in sqMacSSL.c: 248: /* We are connected. Verify the cert. */ 249: ssl->state = SQSSL_CONNECTED; 250: ssl->certFlags = -1; While on Linux, in in sqUnixOpenSSL.c: 292: /* Check the result of verification */ 293: result = SSL_get_verify_result(ssl->ssl); 294: if(ssl->loglevel) printf("sqAcceptSSL: SSL_get_verify_result = %d\n", result); 295: /* FIXME: Figure out the actual failure reason */ 296: ssl->certFlags = result ? SQSSL_OTHER_ISSUE : SQSSL_OK; Still not a full implementation, but better (and others report SqueakSSL is working on Linux). The OpenSSL calls used on Linux seem to exist identically on Mac OS X. (BTW, there are two instances of this code in the C file.) Changing the example code in SqueakSSL class>>google: to skip the certState check: "Verify that the cert is valid" ssl certState = 0 ifFalse:[ self error: 'The certificate is invalid (code: ', ssl certState,')'. ]. Results in a working example. If I only knew how to recompile the plugin I could try to build a better one, I have however never done this (nor built a VM). Is there anybody else interested in helping out ? Sven

Jan. 9, 2011

Re: [Pharo-project] Gofer problem installing packages with the same name

by Lukas Renggli

No, Gofer doesn't look in repositories you don't specify. However, it uses and prefers your local package-cache if it contains a newer version of your package (which is likely the case in your example). You can disable the package-cache by sending something like #disablePackageCache to your Gofer instance (I don't have an image at hand right now, but you find it in the code and documentation). Gofer is part of Pharo and not maintained in my repository anymore. This #update method should be removed it is not supposed to work anymore. Lukas On Sunday, 9 January 2011, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Hi list, > I have some issues with Gofer, maybe already known. When I evaluate: > > Gofer new > Â Â Â Â squeaksource: 'Subjectivity'; > Â Â Â Â package: 'Subjectivity'; > Â Â Â Â load. > > it seems that Gofer takes the first package named Subjectivity it > founds which in this case is > http://www.squeaksource.com/Decisionstrategy.html while I wanted to > take it from http://www.squeaksource.com/Subjectivity.html (please see > the screenshot). > After then I've tried to update "Gofer upgrade" for a fix, but it > seems it cannot connect to http://source.lukas-renggli.ch and then > entered in an endless loop. Any hint? > (Using Pharo1.2beta Latest update: #12294) > > Cheers, > > -- > HernÃ¡n Morales > Information Technology Manager, > Institute of Veterinary Genetics. > National Scientific and Technical Research Council (CONICET). > La Plata (1900), Buenos Aires, Argentina. > Telephone: +54 (0221) 421-1799. > Internal: 422 > Fax: 425-7980 or 421-1799. > -- Lukas Renggli www.lukas-renggli.ch

Jan. 9, 2011