June 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Squeaksource is...

by Fabrizio Perin

Hi, the problem seems to be the server on which squeaksource is, not squeaksource itself. I will restart the server ASAP. Cheers, Fabrizio 2012/6/11 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> > ...down :) > > Can someone take a look, please? > > -- > Bernat Romagosa. >

June 11, 2012

Re: [Pharo-project] Squeaksource is...

by Igor Stasenko

good reminder that i should migrate my stuff to sthub On 11 June 2012 11:05, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> wrote: > ...down :) > > Can someone take a look, please? > > -- > Bernat Romagosa. -- Best regards, Igor Stasenko.

June 11, 2012

Re: [Pharo-project] Look and font competition

by S Krish

As this gif shows, and I prefer, the SBDIC buttons should be hidden away and prefereably as a drop down as it used to be earlier. In normal dev workflow, its rare to slip to using this access and even if its often, I find it to my aesthetic sense a little better to have an usual drop down list.

June 11, 2012

Re: [Pharo-project] FileReference >> #exists not working?

by Esteban Lorenzano

can be related to http://code.google.com/p/pharo/issues/detail?id=5693 so... you should download latest vm to try it. On Jun 11, 2012, at 11:24 AM, Mariano Martinez Peck wrote: > imagine 'foo.txt' file exists in my image directory, if I do: > > 'foo.txt' asFileReference exits -> true. > 'foo.txt' asFileReference delete > (the file is removed from the OS) > 'foo.txt' asFileReference exits -> true. > mmmm shouldn't be false now? > > couldn't debug it yet... sorry > > -- > Mariano > http://marianopeck.wordpress.com >

June 11, 2012

[Pharo-project] FileReference >> #exists not working?

by Mariano Martinez Peck

imagine 'foo.txt' file exists in my image directory, if I do: 'foo.txt' asFileReference exits -> true. 'foo.txt' asFileReference delete (the file is removed from the OS) 'foo.txt' asFileReference exits -> true. mmmm shouldn't be false now? couldn't debug it yet... sorry -- Mariano http://marianopeck.wordpress.com

June 11, 2012

[Pharo-project] Squeaksource is...

by Bernat Romagosa

...down :) Can someone take a look, please? -- Bernat Romagosa.

June 11, 2012

Re: [Pharo-project] recompiling class

by Igor Stasenko

On 11 June 2012 09:26, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > The whole point about improving the system is to then use the improvements. > Else what's the point in improving anything? > Hi, from Capt. Obvious :) > Â Â Â Â Marcus > > -- > Marcus Denker -- http://marcusdenker.de > > -- Best regards, Igor Stasenko.

June 11, 2012

Re: [Pharo-project] [Vm-dev] Re: Plan/discussion/communication around new object format

by Igor Stasenko

Some extra ideas. 1. Avoiding extra header for big sized objects. I not sure about this, but still .. according to Eliot's design: 8: slot size (255 => extra header word with large size) What if we extend size to 16 bits (so in total it will be 65536 slots) and we have a single flag, pointing how to calculate object size: flag(0) object size = (size field) * 8 flag(1) object size = 2^ (slot field) which means that past 2^16 (or how many bits we dedicate to size field in header) all object sizes will be power of two. Since most of the objects will fit under 2^16, we don't lose much. For big arrays, we could have a special collection/array, which will store exact size in it's inst var (and we even don't need to care in cases of Sets/Dicts/OrderedCollections). Also we can actually make it transparent: Array class>>new: size size > (max exact size ) ifTrue: [ ^ ArrayWithBigSizeWhatever new: size ] of course, care must be taken for those variable classes which potentially can hold large amounts of bytes (like Bitmap). But i think code can be quickly adopted to this feature of VM, which will simply fail a #new: primitive if size is not power of two for sizes greater than max "exact size" which can fit into size field of header. ---- 2. Slot for arbitrary properties. If you read carefully, Eliot said that for making lazy become it is necessary to always have some extra space per object, even if object don't have any fields: <<We shall probably keep the minimum object size at 16 bytes so that there is always room for a forwarding pointer. >> So, this fits quite well with idea of having slot for dynamic properties per object. What if instead of "extending object" when it requires extra properties slot, we just reserve the slot for properties at the very beginning: [ header ] [ properties slot] ... rest of data .. so, any object will have that slot. And in case of lazy-become. we can use that slot for holding forwarding pointer. Voila. 3. From 2. we going straight back to hash.. VM don't needs to know such a thing as object's hash, it has no semantic load inside VM, it just answers those bits by a single primitive. So, why it is kind of enforced inherent property of all objects in system? And why nobody asks, if we have that one, why we could not have more than one or as many as we want? This is my central question around idea of having per-object properties. Once VM will guarantee that any object can have at least one slot for storing object reference (property slot), then it is no longer needed for VM to care about identity hash. Because it can be implemented completely at language size. But most of all, we are NO longer limited how big/small hash values , which directly converts into bonuses: less hash collisions > more performance. Want 64-bit hash? 128-bit? Whatever you desire: Object>>identityHash ^ self propertiesAt: #hash ifAbsentPut: [ HashGenerator newHashValue ] and once we could have per-object properties.. and lazy become, things like Magma will get a HUGE benefits straightly out of the box. Because look, lazy become, immutability - those two addressing many problems related to OODB implementation (i barely see other use cases, where immutability would be as useful as in cases of OODB).. so for me it is logical to have this last step: by adding arbitrary properties, OODB now can store the ID there. -- Best regards, Igor Stasenko.

June 11, 2012

Re: [Pharo-project] Look and font competition

by Olivier Auverlot

Anonymous Pro is a cool font for editing code (http://www.ms-studio.com/FontSales/anonymouspro.html) Olivier ;-) > > On Sun, Jun 10, 2012 at 10:27 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Hi guys >> >> this morning Igor shows me all his work around dynlib loading of third party plugins. >> And yes now we get all the third party plugins downloaded and compiled (yes with only one copy of FT2)â¦.Great stuff! >> >> Now we would like to organize a little competition for the official look of Pharo 2.0. So if you feel that you are a little >> bit designer inside, please send us proposals. >> We propose this one :) based on Curlz MT (welcome to the world of the pink little ponies) :) >> >> > <PharoScreenshot.3.png>

June 11, 2012

Re: [Pharo-project] recompiling class

by Tudor Girba

+1. It is in your interest to get us to move to the latest version, and the best way to do it is to keep offering irresistible reasons :) Cheers, Doru On Mon, Jun 11, 2012 at 9:31 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Jun 11, 2012, at 7:17 AM, S Krish wrote: > >> "decompile to an Intermediate Representation" >> >> This will be nice to have backported if possible to 1.4. >> > IR: you can do it. Whole compiler: no way, as it changes APIs > and honestly, life is too short. > > Â Â Â Â Marcus > > -- > Marcus Denker -- http://marcusdenker.de > > -- www.tudorgirba.com "Every thing has its own flow"

June 11, 2012