- Pharo-dev - lists.pharo.org

Re: [Pharo-project] is there an easy way to know the SmallInteger instances?

by Mariano Martinez Peck

On Sun, Nov 21, 2010 at 11:55 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>wrote: > Mariano, > > I see your point, but given the immediate object encoding tricks I'm not > sure it's possible. :( It's a pity. Because most users should not be aware of this. This should be completly transparent for the developer. > Would the class methods #minVal and #maxVal be of any use to you? > No :( Maybe it is better in this way: I want to know how many instances/temp var have a SmallInetger. This means, how many slots/words have a 1 in the last bit. This is what I understand by "Smallinteger instances". > > 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: Sunday, November 21, 2010 4:41 PM > To: Pharo Development > Subject: [Pharo-project] is there an easy way to know the SmallInteger > instances? > > If I do SmallInteger alIInstances I get an empty array, and of course, with > SmallInteger instanceCount I get zero. > > Now, I can understand that from the VM point of view, but for the final > user, this should be polymorphic. For example, for instanceCount, I would > like to know all the "variable slots" that has a 1 in the last bit. > Is this already possible? if true, which message? if not, should I hack > in the vm and code a primitive that does this? > > And the same for allInstances, if I can inspect 5, I should be also to > inspect SmallInteger allInstances, and SmallInteger allInstances first, > etc.... > > thanks > > Mariano > >

Nov. 21, 2010

Re: [Pharo-project] is there an easy way to know the SmallInteger instances?

by Schwab,Wilhelm K

Mariano, I see your point, but given the immediate object encoding tricks I'm not sure it's possible. Would the class methods #minVal and #maxVal be of any use to you? 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: Sunday, November 21, 2010 4:41 PM To: Pharo Development Subject: [Pharo-project] is there an easy way to know the SmallInteger instances? If I do SmallInteger alIInstances I get an empty array, and of course, with SmallInteger instanceCount I get zero. Now, I can understand that from the VM point of view, but for the final user, this should be polymorphic. For example, for instanceCount, I would like to know all the "variable slots" that has a 1 in the last bit. Is this already possible? if true, which message? if not, should I hack in the vm and code a primitive that does this? And the same for allInstances, if I can inspect 5, I should be also to inspect SmallInteger allInstances, and SmallInteger allInstances first, etc.... thanks Mariano

Nov. 21, 2010

Re: [Pharo-project] New to PHP 5.4: Traits

by jaayer

---- On Sun, 21 Nov 2010 13:06:35 -0800 Stefan Marr wrote ---- >Hi: > >On 21 Nov 2010, at 21:47, jaayer wrote: >> Excellent that other, lesser languages like PHP, Perl 6 and Scala have already adopted and standardized Traits while the reactionaries in the Smalltalk community still resist doing the same? >Ignoring all the sarcasm in that comment: >I don't see any form of standardization here. I am not aware that any of the other existing PHP implementations has picked up Traits so far. PHP has no standard; the implementation is the standard, and Traits are being added to the implementation, hence, "standardization." My point remains; other languages are or have already adopted Traits while the Smalltalk community, from which the concept sprang, continues to drag its heels after nearly a decade since their introduction. >And well, it is about 3 years from the first implementation to a first release in an official alpha version of PHP. There is still a loooong way to go... No, there isn't, at least not compared with the rate of Smalltalk's adoption of Traits. Face it. There are just too many Smalltalkers who seem to think the language is a complete revelation that no mortal has the right to amend. Other languages can grow to accommodate new features; Smalltalk, which went through a number major revisions in the 70s at PARC, remains frozen in the amber of 1980. >Best regards >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 > > >

Nov. 21, 2010

[Pharo-project] is there an easy way to know the SmallInteger instances?

by Mariano Martinez Peck

If I do SmallInteger alIInstances I get an empty array, and of course, with SmallInteger instanceCount I get zero. Now, I can understand that from the VM point of view, but for the final user, this should be polymorphic. For example, for instanceCount, I would like to know all the "variable slots" that has a 1 in the last bit. Is this already possible? if true, which message? if not, should I hack in the vm and code a primitive that does this? And the same for allInstances, if I can inspect 5, I should be also to inspect SmallInteger allInstances, and SmallInteger allInstances first, etc.... thanks Mariano

Nov. 21, 2010

Re: [Pharo-project] Cannot upgrade my pharo-core 1.2 'tracking' image to #12234

by Alain Plantec

Hi Sven, It is probably because of some changes I've made in TextEditor. Close all your window and then try again to update. Cheers Alain Le 21/11/2010 16:13, Sven Van Caekenberghe a Ã©crit : > This is probably not very important, but I cannot upgrade my pharo-core 1.2 'tracking' image to #12234. > This image started a long time ago as #12123. > > THERE_BE_DRAGONS_HERE > MessageNotUnderstood: receiver of "characterBlockForIndex:" is nil > 21 November 2010 4:03:32 pm > > VM: Mac OS - intel - 1065 - Croquet Closure Cog VM [CoInterpreter VMMaker-oscog.35] 30.0 > Image: Pharo1.2a [Latest update: #12242] > > SecurityManager state: > Restricted: false > FileAccess: true > SocketAccess: true > Working Dir /Users/sven/apps/Smalltalk/Pharo/Pharo-1.2 > Trusted Dir /foobar/tooBar/forSqueak/bogus/ > Untrusted Dir /foobar/tooBar/forSqueak/bogus/ > > UndefinedObject(Object)>>doesNotUnderstand: #characterBlockForIndex: > Receiver: nil > Arguments and temporary variables: > aMessage: characterBlockForIndex: 17441 > exception: MessageNotUnderstood: receiver of "characterBlockForIndex:" is nil > resumeValue: nil > Receiver's instance variables: > nil > > SmalltalkEditor(TextEditor)>>markIndex: > Receiver: a SmalltalkEditor > Arguments and temporary variables: > > Anybody else seen this ? > I guess I will have to start over now ? > > Sven > > > >

Nov. 21, 2010

Re: [Pharo-project] New to PHP 5.4: Traits

by Stefan Marr

Hi: On 21 Nov 2010, at 21:47, jaayer wrote: > Excellent that other, lesser languages like PHP, Perl 6 and Scala have already adopted and standardized Traits while the reactionaries in the Smalltalk community still resist doing the same? Ignoring all the sarcasm in that comment: I don't see any form of standardization here. I am not aware that any of the other existing PHP implementations has picked up Traits so far. And well, it is about 3 years from the first implementation to a first release in an official alpha version of PHP. There is still a loooong way to go... Best regards 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

Nov. 21, 2010

Re: [Pharo-project] New to PHP 5.4: Traits

by jaayer

---- On Sun, 21 Nov 2010 04:22:51 -0800 StÃ©phane Ducasse wrote ---- >really really excellent! Excellent that other, lesser languages like PHP, Perl 6 and Scala have already adopted and standardized Traits while the reactionaries in the Smalltalk community still resist doing the same? > >On Nov 21, 2010, at 12:22 PM, jaayer wrote: > >> http://simas.posterous.com/new-to-php-54-traits >> >> > > >

Nov. 21, 2010

[Pharo-project] [update 1.2] #12250

by Marcus Denker

12250 ----- Issue 3270: fix xor: to work with blocks and booleans Issue 3277: [FIX] Replace #& in Socket with #and: to save #isConnected send Issue 3180: Failing Tests SUnit -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Nov. 21, 2010

Re: [Pharo-project] Issue 3180 in pharo: Failing Tests SUnit

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3180 by marcus.denker: Failing Tests SUnit http://code.google.com/p/pharo/issues/detail?id=3180 12250

Nov. 21, 2010

Re: [Pharo-project] Issue 3277 in pharo: [FIX] Replace #& in Socket with #and: to save #isConnected send

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3277 by marcus.denker: [FIX] Replace #& in Socket with #and: to save #isConnected send http://code.google.com/p/pharo/issues/detail?id=3277 12250

Nov. 21, 2010