- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3088 in pharo: MNU Text>>withBlanksTrimmed

by pharo＠googlecode.com

Comment #15 on issue 3088 by vonbecm...(a)gmail.com: MNU Text>>withBlanksTrimmed http://code.google.com/p/pharo/issues/detail?id=3088 if you try several times with classes from Announcements-Core, then the query will return more elements each time you follow the steps. an Array(Announcement >> #asAnnouncement Announcement >> #open Announcer >> #announce: Announcer >> #basicSubscribe: Announcer >> #initialize Announcer >> #numberOfSubscriptions Announcer >> #on:do: Announcer >> #on:send:to: Announcer >> #open Announcer >> #removeSubscription: Announcer >> #replace:with: Announcer >> #subscribe:do: Announcer >> #subscribe:send:to: Announcer >> #unsubscribe: Announcer >> #weak Announcer >> #when:do: Announcer >> #announce: Announcer >> #basicSubscribe: Announcer >> #initialize Announcer >> #numberOfSubscriptions Announcer >> #on:do: Announcer >> #on:send:to: Announcer >> #open Announcer >> #removeSubscription: Announcer >> #replace:with: Announcer >> #subscribe:do: Announcer >> #subscribe:send:to: Announcer >> #unsubscribe: Announcer >> #weak Announcer >> #when:do:)

April 11, 2011

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

by Alexandre Bergel

Hi Sven, +1 The exception hierarchy needs some work, indeed. If you make all your new exception a subclass of Error, you should not have a problem with the existing handler I imagine. Alexandre On 11 Apr 2011, at 10:10, Sven Van Caekenberghe wrote: > Hi All, > > I have this idea that I would like to discuss on the next Pharo sprint and maybe start to implement if there is some consensus on it. > > It has been mentioned many times before on this list that Object>>#error: should be replaced by signalling specific Exceptions in as many cases as possible (or where it makes sense). Even today, there was http://code.google.com/p/pharo/issues/detail?id=3987 ! > > I think the core system should set the example here, by defining a number of general purpose exceptions and by using them. Going over #error: senders will be a lot of work but can be done in incremental/Pharo steps. > > So I went over the current hierarchy, scanned quickly through their references and some #error: senders by fundamental classes and looked at some other Smalltalks. I came up with the following very rough draft of an extended hierarchy (** marks new exceptions). In between brackets are the instance variables. Of course, we have to discuss about naming, instance variables and opportunities for reuse and inheritance (could be fun). > > I am no expert on exceptions and would certainly like to learn more. I am probably overlooking some aspects. We have to keep this Smalltalk like, flexible, dynamic, not start mimicing other languages. > > Any step in this direction will be an improvement over the current situation. Really using them correctly throughout the system will take some time. Defining the hierarchy could be done rather quickly. Refactoring is always possible later on. > > Exception (messageText) > Abort > Error > ArithemticError > ZeroDivide (dividend) > FloatingPointException > RangeError ** (from, to) > NaNError ** > FileStreamException (fileName) > FileDoesNotExistException (readOnly) > FileExistsException (fileClass) > CannotDeleteFileException > FileWriteError > FileReadError ** > FileClosedException ** > CannotAccessFileException ** > ReadonlyFileException ** > MessageNotUnderstood (message, receiver) > NonBooleanReceiver (object) > OutOfMemory > Halt > AssertionFailure > BreakPoint > SyntaxError ** !exists! (input, position) > NumberFormatException ** > HeadlessError ** > TimedOut ** (object, operation, timeout) > VerificationException > IllegalOperation ** (operation, object) > SizeMismatch (objects) > LowMemory ** (percentageFree) > SubclassResponsibility ** (message, receiver) > NotYetImplemented ** (message, receiver) > CannotInstanciate ** (class) > ReadOnlyObject ** (object) > OutOfFreeSpace ** (object, size) > 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 ** > > All feedback is welcome. > > Regards, > > Sven > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 11, 2011

Re: [Pharo-project] Issue 3088 in pharo: MNU Text>>withBlanksTrimmed

by pharo＠googlecode.com

Updates: Status: Started Comment #14 on issue 3088 by marcus.d...(a)gmail.com: MNU Text>>withBlanksTrimmed http://code.google.com/p/pharo/issues/detail?id=3088 (No comment was entered for this change.)

April 11, 2011

[Pharo-project] Issue 3990 in pharo: 2 dependencies removed from ToolBuilder: PluggableMenuSpec & PluggableMenuItemSpec

by pharo＠googlecode.com

Status: FixProposed Owner: Benjamin...(a)gmail.com Labels: Milestone-1.3 New issue 3990 by Benjamin...(a)gmail.com: 2 dependencies removed from ToolBuilder: PluggableMenuSpec & PluggableMenuItemSpec http://code.google.com/p/pharo/issues/detail?id=3990 We removed 2 dependencies to ToolBuilder when creating menus. We've decided to keep PluggableMenuSpec & PluggableMenuItemSpec from ToolBuilder. Attachments: LittleCleanInToolBuilderHierarchy.2.cs 2.6 KB

April 11, 2011

Re: [Pharo-project] Issue 3088 in pharo: MNU Text>>withBlanksTrimmed

by pharo＠googlecode.com

Comment #13 on issue 3088 by vonbecm...(a)gmail.com: MNU Text>>withBlanksTrimmed http://code.google.com/p/pharo/issues/detail?id=3088 Pharo image: Pharo1.3a#13140 Virtual machine used: Squeak4.1 of 17 April 2010 [latest update: #9957] Platform Name: unix Class browser used (if applicable): Browser did you follow the steps? because i did and it does not work. steps to reproduce 1. follow the steps to reproduce at the beginning. 2. this MNU 3. execute the query SourcedMethodReference allInstances select: [:each | each stringVersion class == Text ] you will get two methods Attachments: PharoDebug.log 29.9 KB

April 11, 2011

[Pharo-project] UIBuilder Tool

by sourav roy

HiI am new to smalltalk and have got fascinated by itsconcepts.... Can i get any information about how to get the UIBuilder Tool integrated with my Pharo 1.1.1What is the link to download the patch if any.Please help me ASAP.Thanks&regards,Sourav RoyGet Yourself a cool, short @in.com Email ID now!

April 11, 2011

Re: [Pharo-project] Issue 2703 in pharo: Unicode experiments of nicolas cellier on squeak

by pharo＠googlecode.com

Updates: Status: Closed Comment #7 on issue 2703 by marcus.d...(a)gmail.com: Unicode experiments of nicolas cellier on squeak http://code.google.com/p/pharo/issues/detail?id=2703 in 13141

April 11, 2011

Re: [Pharo-project] Issue 3987 in pharo: Use specific KeyNotFoundError in Dictionaries

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3987 by marcus.d...(a)gmail.com: Use specific KeyNotFoundError in Dictionaries http://code.google.com/p/pharo/issues/detail?id=3987 in 13141

April 11, 2011

[Pharo-project] [update 1.3] #13141

by Marcus Denker

13141 ----- Issue 3988: Debugger cannot open because of Decompiler assertion failure Issue 3980: TestResource fails to makeAvailable an never recovers Issue 3987: Use specific KeyNotFoundError in Dictionaries Issue 2703: Unicode experiments of nicolas cellier on squeak -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 11, 2011

Re: [Pharo-project] Issue 3980 in pharo: TestResource fails to makeAvailable an never recovers

by pharo＠googlecode.com

Comment #3 on issue 3980 by marcus.d...(a)gmail.com: TestResource fails to makeAvailable an never recovers http://code.google.com/p/pharo/issues/detail?id=3980 in 13141 TODO: 1.2

April 11, 2011