- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3988 in pharo: Debugger cannot open because of Decompiler assertion failure

by pharo＠googlecode.com

Updates: Status: Closed Comment #3 on issue 3988 by marcus.d...(a)gmail.com: Debugger cannot open because of Decompiler assertion failure http://code.google.com/p/pharo/issues/detail?id=3988 (No comment was entered for this change.)

April 11, 2011

Re: [Pharo-project] Issue 3988 in pharo: Debugger cannot open because of Decompiler assertion failure

by pharo＠googlecode.com

Updates: Labels: Milestone-1.3 Comment #2 on issue 3988 by marcus.d...(a)gmail.com: Debugger cannot open because of Decompiler assertion failure http://code.google.com/p/pharo/issues/detail?id=3988 in 13141

April 11, 2011

Re: [Pharo-project] Brussels Sprint: gathering number of attendes

by Stefan Marr

On 11 Apr 2011, at 17:33, Veronica Isabel Uquillas Gomez wrote: > On 11 Apr 2011, at 11:23, Johan Brichau wrote: >> - Steph >> - Marcus >> - Sven >> - Mariano >> - Craig Latta >> - Thomas Holzer >> - Andy >> - Johan > > -> Veronica -> Stefan -- 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 11, 2011

Re: [Pharo-project] Brussels Sprint: gathering number of attendes

by Veronica Isabel Uquillas Gomez

On 11 Apr 2011, at 11:23, Johan Brichau wrote: > Hi everyone. > > To make sure we have enough food and drinks for everyone. Please make sure to let us know you are coming. > From previous emails, I have understood the following people are attending: > > - Steph > - Marcus > - Sven > - Mariano > - Craig Latta > - Thomas Holzer > - Andy > - Johan -> Veronica

April 11, 2011

Re: [Pharo-project] Issue 3982 in pharo: Error: can''t find EOCD position

by pharo＠googlecode.com

Updates: Status: Closed Comment #5 on issue 3982 by marcus.d...(a)gmail.com: Error: can''t find EOCD position http://code.google.com/p/pharo/issues/detail?id=3982 (No comment was entered for this change.)

April 11, 2011

[Pharo-project] Issue 3989 in pharo: Fix the scrollToView method

by pharo＠googlecode.com

Status: FixProposed Owner: Benjamin...(a)gmail.com Labels: Nautilus New issue 3989 by Benjamin...(a)gmail.com: Fix the scrollToView method http://code.google.com/p/pharo/issues/detail?id=3989 Like that, even if the method has been chooser without using the keyboard/mouse, the selection is shown "properly" Because it's hard to reproduce, I'm not sure it fix totally the issue, but I'm testing it right now, and if some of you want to test it, you're welcome Attachments: MorphTreeMorph.BenjaminVanRyseghem.2.cs 424 bytes

April 11, 2011

[Pharo-project] Improving Pharo's Exception Hierarchy

by Sven Van Caekenberghe

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

April 11, 2011

Re: [Pharo-project] Issue 3988 in pharo: Debugger cannot open because of Decompiler assertion failure

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #1 on issue 3988 by nicolas....(a)gmail.com: Debugger cannot open because of Decompiler assertion failure http://code.google.com/p/pharo/issues/detail?id=3988 Name: SLICE-Issue-3988-DebuggerCannotOpenBecauseOfDecompilerAssertionFailure-nice.1 Dependencies: Compiler-nice.282 This is the fix from squeak (Compiler.nice.130)

April 11, 2011

[Pharo-project] Issue 3988 in pharo: Debugger cannot open because of Decompiler assertion failure

by pharo＠googlecode.com

Status: Accepted Owner: nicolas....(a)gmail.com Labels: Type-Squeak New issue 3988 by nicolas....(a)gmail.com: Debugger cannot open because of Decompiler assertion failure http://code.google.com/p/pharo/issues/detail?id=3988 This was reported at http://bugs.squeak.org/view.php?id=7467 If you try to debug this, then your image might hang: '1 0' readStream in: [ :input | | i | [ input skipSeparators. i := Integer readFrom: input. i = 0 ] whileFalse: [ | k count digits | k := 1. count := 0. digits := Array new: 10 withAll: 0. [ count < i ] whileTrue: [ | index1 ps | ps := k printString. ((index1 := ps indexOf: $1) = 0 or: [ (ps indexOf: $3 startingAt: index1) = 0 ]) ifTrue: [ count := count + 1. ps do: [ :each | digits at: each asciiValue - 47 put: (digits at: each asciiValue - 47) + 1 ] ]. k := k + 1 ]. self halt ] ]

April 11, 2011

Re: [Pharo-project] Issue 3982 in pharo: Error: can''t find EOCD position

by pharo＠googlecode.com

Comment #4 on issue 3982 by vonbecm...(a)gmail.com: Error: can''t find EOCD position http://code.google.com/p/pharo/issues/detail?id=3982 i tried again several times, and now it works. Sorry, i cannot reproduce it anymore. you can close it.

April 11, 2011