December 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 2247 in pharo: MessageNotUnderstood: NewInspector class>>openOn:withEvalPane:withLabel:

by pharo＠googlecode.com

Updates: Status: Started Labels: -Milestone-1.1 Milestone-1.2-DevImage Comment #4 on issue 2247 by marcus.denker: MessageNotUnderstood: NewInspector class>>openOn:withEvalPane:withLabel: http://code.google.com/p/pharo/issues/detail?id=2247 The problem is the NewInspector. Dev 1.2 should be build without it.

Dec. 13, 2010

Re: [Pharo-project] Is SmallInteger a really too dangerous class?

by Mariano Martinez Peck

Ups....you are right bill, my example was wrong....it should be: SmallInteger class >> initialize self addInstVarName: 'Zaraza'. On Mon, Dec 13, 2010 at 10:05 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Mon, Dec 13, 2010 at 9:42 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>wrote: > >> Mariano, >> >> SmallInteger is handled as (in Dolphin parlance) as an immediate object, >> meaning that they are encoded entirely in the object pointer; as such, they >> can't have instance variables. Object cannot have ivs either, because it >> has subclasses that are so constrained. >> > > Hi Bill, thanks. Yes, in SqueakVM it is the same...but I am adding an > instVar to the SmallInteger CLASS, not to their instances ;) > but still...,maybe the VM assumes that the SmallInteger CLASS is of certain > fixed size. > > mariano > > >> >> Bill >> >> >> ________________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr [ >> pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Mariano >> Martinez Peck [marianopeck(a)gmail.com] >> Sent: Monday, December 13, 2010 3:16 PM >> To: Pharo Development; Squeak Development Discussion Virtual Machine >> Subject: [Pharo-project] Is SmallInteger a really too dangerous class? >> >> Hi folks. Sorry for the cross-post, I am not sure if it is image or vm >> problem. >> >> If I implement this: >> >> SmallInteger >> initialize >> self addInstVarName: 'Zaraza'. >> >> I have the error: 'SmallInteger cannot be changed' >> >> This is because SmallInteger is in the ClassBuilder >> tooDangerousClasses >> and the error is in ClassBuilder >> name: className inEnvironment: env >> subclassOf: newSuper type: type instanceVariableNames: instVarString >> classVariableNames: classVarString poolDictionaries: poolString category: >> category unsafe: unsafe >> >> Now....since this is Smalltalk, I can just comment something, continue, or >> any other kind of hack so that I can add class variables to SmallInetger. >> For my CompiledMethod proxies stuff, I am using SmallIntegers and I have >> some crashes (one is due to a corrupt heap and Eliot said something about >> sizes)...I wonder if this is related to this...So the question is: is >> really SMallInteger a too dangerous class so that it cannot be changed? not >> even adding a class variable??? does the VM assume that the class >> SmallInetger has a fixed size? if true, where? >> >> Thanks in advance >> >> Mariano >> >> >

Dec. 13, 2010

Re: [Pharo-project] Is SmallInteger a really too dangerous class?

by Mariano Martinez Peck

On Mon, Dec 13, 2010 at 9:42 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>wrote: > Mariano, > > SmallInteger is handled as (in Dolphin parlance) as an immediate object, > meaning that they are encoded entirely in the object pointer; as such, they > can't have instance variables. Object cannot have ivs either, because it > has subclasses that are so constrained. > Hi Bill, thanks. Yes, in SqueakVM it is the same...but I am adding an instVar to the SmallInteger CLASS, not to their instances ;) but still...,maybe the VM assumes that the SmallInteger CLASS is of certain fixed size. mariano > > Bill > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [ > pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Mariano Martinez > Peck [marianopeck(a)gmail.com] > Sent: Monday, December 13, 2010 3:16 PM > To: Pharo Development; Squeak Development Discussion Virtual Machine > Subject: [Pharo-project] Is SmallInteger a really too dangerous class? > > Hi folks. Sorry for the cross-post, I am not sure if it is image or vm > problem. > > If I implement this: > > SmallInteger >> initialize > self addInstVarName: 'Zaraza'. > > I have the error: 'SmallInteger cannot be changed' > > This is because SmallInteger is in the ClassBuilder >> tooDangerousClasses > and the error is in ClassBuilder >> name: className inEnvironment: env > subclassOf: newSuper type: type instanceVariableNames: instVarString > classVariableNames: classVarString poolDictionaries: poolString category: > category unsafe: unsafe > > Now....since this is Smalltalk, I can just comment something, continue, or > any other kind of hack so that I can add class variables to SmallInetger. > For my CompiledMethod proxies stuff, I am using SmallIntegers and I have > some crashes (one is due to a corrupt heap and Eliot said something about > sizes)...I wonder if this is related to this...So the question is: is > really SMallInteger a too dangerous class so that it cannot be changed? not > even adding a class variable??? does the VM assume that the class > SmallInetger has a fixed size? if true, where? > > Thanks in advance > > Mariano > >

Dec. 13, 2010

Re: [Pharo-project] Issue 3288 in pharo: OB does not work with editor changes

by pharo＠googlecode.com

Updates: Status: Closed Comment #6 on issue 3288 by marcus.denker: OB does not work with editor changes http://code.google.com/p/pharo/issues/detail?id=3288 This particular bug has been fixed.

Dec. 13, 2010

Re: [Pharo-project] Issue 2928 in pharo: Trying to change the category of traits method -> DNU

by pharo＠googlecode.com

Updates: Status: Duplicate Mergedinto: 3367 Comment #4 on issue 2928 by marcus.denker: Trying to change the category of traits method -> DNU http://code.google.com/p/pharo/issues/detail?id=2928 (No comment was entered for this change.)

Dec. 13, 2010

Re: [Pharo-project] Issue 3367 in pharo: PopupChoiceDialogWindow>>handlesKeyboard: fails with empty label list

by pharo＠googlecode.com

Comment #5 on issue 3367 by marcus.denker: PopupChoiceDialogWindow>>handlesKeyboard: fails with empty label list http://code.google.com/p/pharo/issues/detail?id=3367 Issue 2928 has been merged into this issue.

Dec. 13, 2010

Re: [Pharo-project] Issue 2928 in pharo: Trying to change the category of traits method -> DNU

by Alain Plantec

Le 13/12/2010 21:17, pharo(a)googlecode.com a Ã©crit : > > Comment #3 on issue 2928 by marcus.denker: Trying to change the > category of traits method -> DNU > http://code.google.com/p/pharo/issues/detail?id=2928 > > looks strange to fix this so deep in the system... it should be fixed > earlier > > > I think it is already fixed, see issue 3367 <http://code.google.com/p/pharo/issues/detail?id=3367>. Cheers Alain

Dec. 13, 2010

Re: [Pharo-project] Is SmallInteger a really too dangerous class?

by Schwab,Wilhelm K

Mariano, SmallInteger is handled as (in Dolphin parlance) as an immediate object, meaning that they are encoded entirely in the object pointer; as such, they can't have instance variables. Object cannot have ivs either, because it has subclasses that are so constrained. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck [marianopeck(a)gmail.com] Sent: Monday, December 13, 2010 3:16 PM To: Pharo Development; Squeak Development Discussion Virtual Machine Subject: [Pharo-project] Is SmallInteger a really too dangerous class? Hi folks. Sorry for the cross-post, I am not sure if it is image or vm problem. If I implement this: SmallInteger >> initialize self addInstVarName: 'Zaraza'. I have the error: 'SmallInteger cannot be changed' This is because SmallInteger is in the ClassBuilder >> tooDangerousClasses and the error is in ClassBuilder >> name: className inEnvironment: env subclassOf: newSuper type: type instanceVariableNames: instVarString classVariableNames: classVarString poolDictionaries: poolString category: category unsafe: unsafe Now....since this is Smalltalk, I can just comment something, continue, or any other kind of hack so that I can add class variables to SmallInetger. For my CompiledMethod proxies stuff, I am using SmallIntegers and I have some crashes (one is due to a corrupt heap and Eliot said something about sizes)...I wonder if this is related to this...So the question is: is really SMallInteger a too dangerous class so that it cannot be changed? not even adding a class variable??? does the VM assume that the class SmallInetger has a fixed size? if true, where? Thanks in advance Mariano

Dec. 13, 2010

Re: [Pharo-project] Issue 1042 in pharo: documentation/help menu

by pharo＠googlecode.com

Comment #8 on issue 1042 by tony.fleig: documentation/help menu http://code.google.com/p/pharo/issues/detail?id=1042 I have completed my survey of shortcut keys on Linux, OS X, and Windows. I have attached a PDF of the results. You can also view the spreadsheet on-line here: https://spreadsheets.google.com/ccc?key=0AobjLM-R40Z1dERucVk4YzlhUHRQWE9HX0…. TF Attachments: Pharo Shortcut Keys.pdf 79.8 KB

Dec. 13, 2010

Re: [Pharo-project] Issue 1213 in pharo: Unable to type some czech characters

by pharo＠googlecode.com

Updates: Labels: Milestone-1.2 Comment #18 on issue 1213 by marcus.denker: Unable to type some czech characters http://code.google.com/p/pharo/issues/detail?id=1213 (No comment was entered for this change.)

Dec. 13, 2010