- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Are you a Pharo contributor ??? [WAS] Re: Pharo Open Source Smalltalk â Contributors

by Diogenes Moreira

Ok.. Well DiÃ³genes Alberto Moreira CTO at Ilon S.A. and CTO at Sociadad Anonima para la Salud S.A. ( www.ilon.com.ar) Contributor on DBXTalk (http://squeakdbx.org) and other projects. Smalltalker And Pharo's lover :) Best On Thu, Apr 14, 2011 at 10:46 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > if true...then what are you wainting for? > > http://www.pharo-project.org/community/contributors > > Send you data and nice picture :) > > Seriously, it is important for marketing among other things. Imagine you > arrive to a new project...it is good to see that there are several > contributing to it. Probably this page is not the best, but is something > more. > > Mariano > > > > On Wed, Apr 13, 2011 at 8:18 PM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > >> Added ! >> >> Laurent. >> >> On Wed, Apr 13, 2011 at 6:45 PM, Juan Vuletich <juan(a)jvuletich.org>wrote: >> >>> Hi Laurent, >>> >>> I'd like to be added to >>> http://www.pharo-project.org/community/contributors . My picture is >>> attached. Description text could be "Contributed the default anti-aliased >>> fonts and the SimpleMorphic UI framework. Web page at www.jvuletich.org >>> ". >>> >>> Thank you. >>> >>> Cheers, >>> Juan Vuletich >>> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > >

April 14, 2011

Re: [Pharo-project] Improving Pharo's Exception Hierarchy

by Dale Henrichs

Cesar, Good point. Exception handling code even when using simple class-based exceptions and exception sets does indeed devolve into CaseOf constructs. Using classes, the following code is still common: [ (RangeError new) signal: 'access out of bounds' ] on: Error do: [:ex | (ex isKindOf: RangeError) ifTrue: [ "do your thang" ] ifFalse: [ ex pass ]]. and using ExceptionSets doesn't lead to anything better. At GemStone we _have_ added an extention that looks something like the following to get away from explicit CaseOf code: [ (NumericError new) reason: #rangeError; signal: 'access out of bounds' ] onExceptions: NaNError, RangeError do: { [:naNError | "do something with NANError"]. [:rangeError | "o something with RangeError"]. }. but it's just a different form of CaseOf...I don't think the use of reasonCodes is the cause... To get around this, I guess you'd have to start extending various Exception classes with "handler-specific" methods that would allow you to double dispatch your way out of the CaseOf construct... Dale n 04/14/2011 12:38 PM, csrabak(a)bol.com.br wrote: > Not willing to rattle cages, reading this particular set of postings > I wonder if its my sole feeling or this kind of code 'leads to' > naturally to a screaming need for a CaseOf construct? > > In the snippet below submitted by Dale if we have some other > [expected] numeric errors (a.k.a. 'reasons') you would end up with a > very hairy entanglement of ifTrue:[]ifFalse:[], wouldn't you? > > my 0.01999..... > > -- Cesar Rabak > > > Em 14/04/2011 15:52, Dale Henrichs< dhenrich(a)vmware.com> escreveu: > Stef, > > For rangeError the code would look like this: > > [ (NumericError new) reason: #rangeError; signal: 'access out of > bounds' ] on: NumericError do: [:ex | ex reasonCode == #rangeError > ifTrue: [ "do your thang" ] ifFalse: [ ex pass ]]. > > Dale > > On 04/14/2011 11:13 AM, StÃ©phane Ducasse wrote: >> Dale >> >> so it means that I write what? >> >> [] on: NumericError do: [:ex | ] >> >> how do I access the rangeError? >> >> >>>> >>> >>> Using Sven's hierachy as a starting point and taking some cues >>> from the GemStone exception hierarchy, I would suggest the >>> following (names atarting with # are reasonCodes in the namespace >>> of the parent exception class, instead of a unique class): >>> >>> Exception (messageText reasonCode) Abort Error NumericError >>> #floatingPointException #rangeError #naNError ZeroDivide >>> (dividend) FileStreamException (fileName) >>> #fileDoesNotExistException #fileExistsException (fileClass) >>> #cannotDeleteFileException #fileWriteError #fileReadError ** >>> #fileClosedException ** #cannotAccessFileException ** >>> #readonlyFileException ** MessageNotUnderstood (message, >>> receiver) #nonBooleanReceiver (object) OutOfMemory< handlers?> >>> ControlInterrupt Halt AssertionFailure BreakPoint CompileError >>> SyntaxError ** !exists! (input, position) #numberFormatException >>> ** #headlessError ** TimedOut ** (object, operation, timeout) >>> VerificationException IllegalOperation ** (operation, object) >>> #sizeMismatch (objects) #subclassResponsibility ** (message, >>> receiver) #notYetImplemented ** (message, receiver) >>> #cannotInstanciate ** (class) #readOnlyObject ** (object) >>> OutOfFreeSpace ** #invalidArgument ** (message, receiver, >>> argument) #notIndexable ** (object) #noKeyedAccess ** (object) >>> #nonIntegerIndex ** (receiver, index) #subscriptOutOfBounds ** >>> (receiver, index, from, to) NotFoundException ** (receiver, >>> object) #keyNotFound ** #valueNotFound ** #elementNotFound ** >>> StreamException (stream) #positionError ** (index, from, to) >>> EndOfStream ** #beginOfStream ** >>> >>> Notification Admonition LowMemory ** >>> >> >> > > > >

April 14, 2011

Re: [Pharo-project] [COTDC] 47 - TAssertable

by laurent laffont

On Wed, Apr 13, 2011 at 9:53 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Wed, Apr 13, 2011 at 9:28 PM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > >> On Tue, Apr 12, 2011 at 10:14 PM, laurent laffont < >> laurent.laffont(a)gmail.com> wrote: >> >>> Today: TAssertable >>> >> >> Is it used ? Could not find any reference. >> >> > I think it is not used yet. I think it is a Trait so that we can make > things assertable and not need to subclass from TestCase for example. I may > expect that TestCase uses such Trait instead of implementing all those > methods, but it is not the case. Even more, TAssertable users size -> 0. > > So...seems a work half done. Adrian Kuhn introduce it. Check > > http://forum.world.st/template/NamlServlet.jtp?macro=search_page&node=12948… > > OK I put your answer as comment. Laurent. > Cheers > > Mariano > > >> >> Laurent. >> >> >> >> >>> >>> Comment Of The Day Contest - One Day One Comment >>> Rules: >>> #1: Each day a not commented class is elected. Each day the best comment >>> will be integrated with name of the author(s). >>> #2: If you cannot comment it, deprecate it. >>> Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest >>> >>> Laurent >>> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > >

April 14, 2011

Re: [Pharo-project] Are you a Pharo contributor ??? [WAS] Re: Pharo Open Source Smalltalk â Contributors

by laurent laffont

Done Laurent. On Thu, Apr 14, 2011 at 3:56 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > Oh, well... > > Esteban Lorenzano > Owner of Smallworks (http://smallworks.com.ar) > Author of Mars (http://smallworks.com.ar/en/community/Mars) > Contributor on several projects, like DBXTalk (http://squeakdbx.org) etc. > We use Pharo for everything we do :) > > And here is my picture: > > > > El 14/04/2011, a las 10:46a.m., Mariano Martinez Peck escribiÃ³: > > if true...then what are you wainting for? > > http://www.pharo-project.org/community/contributors > > Send you data and nice picture :) > > Seriously, it is important for marketing among other things. Imagine you > arrive to a new project...it is good to see that there are several > contributing to it. Probably this page is not the best, but is something > more. > > Mariano > > > > On Wed, Apr 13, 2011 at 8:18 PM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > >> Added ! >> >> Laurent. >> >> On Wed, Apr 13, 2011 at 6:45 PM, Juan Vuletich <juan(a)jvuletich.org>wrote: >> >>> Hi Laurent, >>> >>> I'd like to be added to >>> http://www.pharo-project.org/community/contributors . My picture is >>> attached. Description text could be "Contributed the default anti-aliased >>> fonts and the SimpleMorphic UI framework. Web page at www.jvuletich.org >>> ". >>> >>> Thank you. >>> >>> Cheers, >>> Juan Vuletich >>> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > > >

April 14, 2011

Re: [Pharo-project] Improving Pharo's Exception Hierarchy

by Dale Henrichs

On 04/14/2011 12:04 PM, Henrik Sperre Johansen wrote: > On 14.04.2011 20:52, Dale Henrichs wrote: >> Stef, >> >> For rangeError the code would look like this: >> >> [ >> (NumericError new) >> reason: #rangeError; >> signal: 'access out of bounds' >> ] >> on: NumericError >> do: [:ex | >> ex reasonCode == #rangeError >> ifTrue: [ "do your thang" ] >> ifFalse: [ ex pass ]]. >> >> Dale > > Why not use #tag, which is already ANSI? > > Cheers, > Henry > At GemStone we decided not to use tag (we had several cats to skin), but tag could certainly be used... Dale

April 14, 2011

Re: [Pharo-project] presentation

by laurent laffont

On Thu, Apr 14, 2011 at 9:16 PM, Santiago Bragagnolo < santiagobragagnolo(a)gmail.com> wrote: > > Hi Pharo friends, I'm Santiago Bragagnolo from Argentina. (Colleague of > some users of this list from Argentina too) > > I'm currently teaching smalltalk in UTN and getting deep in this amazing > world. So, i want to contribute to pharo comunity, fixing issues, developing > new features, etc. Ok, how can achive mi goals xD? (too formal? sorry if my > english is not enough clear or usual :) ) > Hi Santiago, to fix issues see: http://www.pharocasts.com/2010/03/how-to-contribute-to-pharo.html Blogs and documentation are always nice ;) Laurent. > Greetings. > > Santiago. > > >

April 14, 2011

Re: [Pharo-project] Improving Pharo's Exception Hierarchy

by csrabak＠bol.com.br

Not willing to rattle cages, reading this particular set of postings I wonder if its my sole feeling or this kind of code 'leads to' naturally to a screaming need for a CaseOf construct? In the snippet below submitted by Dale if we have some other [expected] numeric errors (a.k.a. 'reasons') you would end up with a very hairy entanglement of ifTrue:[]ifFalse:[], wouldn't you? my 0.01999..... -- Cesar Rabak Em 14/04/2011 15:52, Dale Henrichs < dhenrich(a)vmware.com > escreveu: Stef, For rangeError the code would look like this: [ (NumericError new) reason: #rangeError; signal: 'access out of bounds' ] on: NumericError do: [:ex | ex reasonCode == #rangeError ifTrue: [ "do your thang" ] ifFalse: [ ex pass ]]. Dale On 04/14/2011 11:13 AM, StÃ©phane Ducasse wrote: > Dale > > so it means that I write what? > > [] on: NumericError do: [:ex | ] > > how do I access the rangeError? > > >>> >> >> Using Sven's hierachy as a starting point and taking some cues from the GemStone exception hierarchy, I would suggest the following (names atarting with # are reasonCodes in the namespace of the parent exception class, instead of a unique class): >> >> Exception (messageText reasonCode) >> Abort >> Error >> NumericError >> #floatingPointException >> #rangeError >> #naNError >> ZeroDivide (dividend) >> FileStreamException (fileName) >> #fileDoesNotExistException >> #fileExistsException (fileClass) >> #cannotDeleteFileException >> #fileWriteError >> #fileReadError ** >> #fileClosedException ** >> #cannotAccessFileException ** >> #readonlyFileException ** >> MessageNotUnderstood (message, receiver) >> #nonBooleanReceiver (object) >> OutOfMemory< handlers?> >> ControlInterrupt >> Halt >> AssertionFailure >> BreakPoint >> CompileError >> SyntaxError ** !exists! (input, position) >> #numberFormatException ** >> #headlessError ** >> TimedOut ** (object, operation, timeout) >> VerificationException >> IllegalOperation ** (operation, object) >> #sizeMismatch (objects) >> #subclassResponsibility ** (message, receiver) >> #notYetImplemented ** (message, receiver) >> #cannotInstanciate ** (class) >> #readOnlyObject ** (object) >> OutOfFreeSpace ** >> #invalidArgument ** (message, receiver, argument) >> #notIndexable ** (object) >> #noKeyedAccess ** (object) >> #nonIntegerIndex ** (receiver, index) >> #subscriptOutOfBounds ** (receiver, index, from, to) >> NotFoundException ** (receiver, object) >> #keyNotFound ** >> #valueNotFound ** >> #elementNotFound ** >> StreamException (stream) >> #positionError ** (index, from, to) >> EndOfStream ** >> #beginOfStream ** >> >> Notification >> Admonition >> LowMemory ** >> > >

April 14, 2011

Re: [Pharo-project] Magma

by Elliot Finley

On Thu, Apr 14, 2011 at 1:51 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > FYI: Chris Muller plans to update Magma for Pharo 1.2 > > http://lists.squeakfoundation.org/pipermail/magma/2011-April/001756.html > > We now get more package maintainers to see value in supporting Pharo > and I think this is a good thing If you read that entire message, you'll see that he doesn't intend to support Pharo beyond 1.2 without either A) compensation or B) developers from Pharo to do the support.

April 14, 2011

[Pharo-project] Issue 4023 in pharo: 'Transcript clear' prints 'Transcript' after clearing prior text

by pharo＠googlecode.com

Status: New Owner: ---- New issue 4023 by DougEdmu...(a)gmail.com: 'Transcript clear' prints 'Transcript' after clearing prior text http://code.google.com/p/pharo/issues/detail?id=4023 Pharo image: Pharo | Pharo-core Pharo core version: Pharo1.3a Latest update: #13144 Virtual machine used: PHaro4.1.1 on Win32 Class browser used (if applicable): "SystemBrowser default" Steps to reproduce: 1. Open a transcript 2. Open a workspace. Send some text to transcript, i.e., Transcript show: 'hello'; cr. 3. Type 'Transcript clear.' in workspace Result: All prior text removed, but now the word "Transcript" appears.

April 14, 2011

[Pharo-project] presentation

by Santiago Bragagnolo

Hi Pharo friends, I'm Santiago Bragagnolo from Argentina. (Colleague of some users of this list from Argentina too) I'm currently teaching smalltalk in UTN and getting deep in this amazing world. So, i want to contribute to pharo comunity, fixing issues, developing new features, etc. Ok, how can achive mi goals xD? (too formal? sorry if my english is not enough clear or usual :) ) Greetings. Santiago.

April 14, 2011