- Pharo-dev - lists.pharo.org

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

by Camillo Bruni

On 2011-04-13, at 18:55, Miguel CobÃ¡ wrote: > El miÃ©, 13-04-2011 a las 14:52 +0200, Camillo Bruni escribiÃ³: > >> And as Mariano pointed out, there should be a convention on the >> naming: I am still not sure about suffixing the exception classes with >> "Exception", but I guess this is a good thing to do. Though I must say >> that I omitted it so far ;) and just put the verb there, but that can >> be easily changed. > > I would say no to suffixes. Analogous to announcements, they shouldn't > have the suffix. The name should be descriptive enough and intention > revealing that the suffix isn't needed in most cases. For example, I > think that > > DividedByZero > > is better than > > DividedByZeroException > > and no information is lost with the sorter name. Instead, DivideByZero > isn't clear enough to indicate that is a event that happened. > > What do you think? If this has been applied in the same sense before and its not a big deal I would prefer no suffixes as well. camillo

April 13, 2011

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

by Miguel CobÃ¡

El miÃ©, 13-04-2011 a las 14:52 +0200, Camillo Bruni escribiÃ³: > And as Mariano pointed out, there should be a convention on the > naming: I am still not sure about suffixing the exception classes with > "Exception", but I guess this is a good thing to do. Though I must say > that I omitted it so far ;) and just put the verb there, but that can > be easily changed. I would say no to suffixes. Analogous to announcements, they shouldn't have the suffix. The name should be descriptive enough and intention revealing that the suffix isn't needed in most cases. For example, I think that DividedByZero is better than DividedByZeroException and no information is lost with the sorter name. Instead, DivideByZero isn't clear enough to indicate that is a event that happened. What do you think? -- Miguel CobÃ¡ http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx

April 13, 2011

Re: [Pharo-project] Issue 4003 in pharo: Build of Core 1.3 broken because of integration of 13147

by pharo＠googlecode.com

Updates: Status: Closed Comment #8 on issue 4003 by marcus.d...(a)gmail.com: Build of Core 1.3 broken because of integration of 13147 http://code.google.com/p/pharo/issues/detail?id=4003 fixed

April 13, 2011

[Pharo-project] Issue 4006 in pharo: Some UI improvement

by pharo＠googlecode.com

Status: FixProposed Owner: Benjamin...(a)gmail.com Labels: Nautilus New issue 4006 by Benjamin...(a)gmail.com: Some UI improvement http://code.google.com/p/pharo/issues/detail?id=4006 - Extraction of a method in IconicButton to allow subclasses to easily redefine the extra border. - a forgotten change set about PluggableMenuItemSpec to allow the enablement to depend of a block without be forced of building the whole menu again Attachments: IconicButtonImprovement.1.cs 728 bytes PluggableMenuItemSpec.BenjaminVanRyseghem.1.cs 1.1 KB

April 13, 2011

[Pharo-project] new transcript :(

by StÃ©phane Ducasse

hi guys why there is no scrollbar on the widgets? why I cannot select text there? why I cannot delete text there? Stef

April 13, 2011

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

by StÃ©phane Ducasse

> You probably know the PharoByExample chapter on exceptions, >> but just in case: https://gforge.inria.fr/frs/download.php/26600/PBE2-Exceptions-2010-03-02.p… > > Seems like the right kind of preparation, I will reread it. > I love written documentation. me too :) this is why I write it and I would love to have a chapter on Zinc for the new book :). > Thanks! > > Sven > > >

April 13, 2011

Re: [Pharo-project] Meanwhile, at another vm

by Stefan Marr

Hi: On 13 Apr 2011, at 16:44, Mariano Martinez Peck wrote: > > "Running on the JVM" and "Running on the JVM" are two completely different things. > Here seems to be the same > > 'Running on the JVM' = 'Running on the JVM' -> true > > ehehhe I guess you forgot to change something or I am so stupid to understand... Sorry, that was on purpose. 'Running on the JVM' is just a useless term. Potato shows how to implement an interpreter in Java that runs on top of the JVM. With some minor adaptations it would also be able to run Pharo. But the question is, how useful would that be. With that model, it is not directly possible to exploit JVM mechanism like threads. It is basically identical to the SqueakVM with just exchanging C for Java. Even compiling Smalltalk to Java bytecode does not get you closer to leveraging the JVM. It would be 'just' Cog, with JVM bytecodes as a target instead of x86. You get speed, but you do not really get closer to use the JVM platform. Best regards Stefan > > Just a reminder: > http://news.squeak.org/2008/07/07/potato-version-of-jsqueak-from-hpi/ PS: It would be awesome if my mail client would be able to quote your mail correctly. -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

April 13, 2011

Re: [Pharo-project] Play and crash

by laurent laffont

Cool ! Thank you all ! Have put this at http://magaloma.blogspot.com/2011/04/polymorph-counter-example.html http://magaloma.blogspot.com/2011/04/petite-horloge-revisited.html Laurent. On Wed, Apr 13, 2011 at 4:25 PM, Henrik Sperre Johansen < henrik.s.johansen(a)veloxit.no> wrote: > On 13.04.2011 16:16, laurent laffont wrote: > >> This works: >> >> counter := Class new >> superclass: Object; >> addInstVarNamed: 'counter'; >> compile: 'initialize >> counter := 0'; >> compile: 'counterString >> ^ counter asString'; >> compile: 'increment >> counter := counter + 1. >> self changed:#counterString'; >> compile: 'decrement >> counter := counter - 1. >> self changed:#counterString'; >> new. >> >> (UITheme builder newColumn: { >> UITheme builder newLabelFor: counter getLabel: #counterString getEnabled: >> nil. >> UITheme builder newRow: { >> UITheme builder newButtonFor: counter action: #increment label: '+' >> help: nil. >> UITheme builder newButtonFor: counter action: #decrement label: '-' >> help: nil. >> } >> }) openInWindowLabeled: 'Counter example'. >> >> >> >> This one crashes the VM (tried on PharoOneClick 1.2 OSX, Cog and StackVM): >> >> (Class new >> superclass: StringMorph; >> compile: 'step self contents: Time now printString'; >> new) >> openCenteredInWorld >> >> >> >> Any idea ? >> > > http://forum.world.st/test-crashing-the-cog-vm-td3393032.html > Answer in first reply :) > > Cheers, > Henry > >

April 13, 2011

[Pharo-project] isHealthy

by StÃ©phane Ducasse

Hi igor this is strange I have a dictionary whose array contains nil and still isHealthy returns true. can an array of a dictionary contains nil? Stef

April 13, 2011

Re: [Pharo-project] Meanwhile, at another vm

by Mariano Martinez Peck

On Wed, Apr 13, 2011 at 4:21 PM, Stefan Marr <pharo(a)stefan-marr.de> wrote: > > On 13 Apr 2011, at 09:32, Philippe Marschall wrote: > > Probably not. I mean you all the code relying on primitives, all the > > code relying on ByteString having the same memory layout as ByteArray, > > all the code relying on the scheduler being non-preemptive, all the > > code relying on #become: and so forth. > > "Running on the JVM" and "Running on the JVM" are two completely different > things. > > Here seems to be the same 'Running on the JVM' = 'Running on the JVM' -> true ehehhe I guess you forgot to change something or I am so stupid to understand... > Just a reminder: > http://news.squeak.org/2008/07/07/potato-version-of-jsqueak-from-hpi/ > > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > > > -- Mariano http://marianopeck.wordpress.com

April 13, 2011