Applying the 11281-11284 updates seems to leave exactly one entry in the
SystemDictionary in the wrong place (too high by one) in the array.
Which entry depends on the image. In the downloadable 11284 image it's
#MCPTest.
I haven't been able to determine how this happens, but executing:
Sma
Bill,
the "no matching versins" message means that there are no "stable" versions
available, so the project is under development and is changing...
If you want to try it anyway ... it _is_ under active development.
You can load an explicit version using the loader ... look at the config and
se
>
>
>>> Thanks Bryce!!! would be cool to have the "official" Linux VM for Pharo
>>> 1.0 release with this feature.
>>>
>>
>>
>> I've built one here
>> http://lolgzs.free.fr/pharo/Squeak-3.11.3.2135-src-pached.tar.gz with
>> FT2Plugin and the patched bitlbt.
>>
>>
> Excellent!!! do you know if thi
2010/3/22 laurent laffont
>
>
> 2010/3/22 Mariano Martinez Peck
>
>
>>
>> On Mon, Mar 22, 2010 at 9:22 PM, Bryce Kampjes > > wrote:
>>
>>> On Thu, 2010-03-11 at 10:28 +0100, Mariano Martinez Peck wrote:
>>> > Both really interesting posts. Now...Some people reported that the
>>> > Exupery Linux
On Mon, Mar 22, 2010 at 2:54 PM, Nicolas Cellier <
nicolas.cellier.aka.n...@gmail.com> wrote:
> You might also want to check last code published in trunk.
>
I saw that. You're eliminating closeTo: for float comparison which seems
fine to me :) Thanks Nicolas!
However, it is indicative that a re
2010/3/22 Mariano Martinez Peck
>
>
> On Mon, Mar 22, 2010 at 9:22 PM, Bryce Kampjes
> wrote:
>
>> On Thu, 2010-03-11 at 10:28 +0100, Mariano Martinez Peck wrote:
>> > Both really interesting posts. Now...Some people reported that the
>> > Exupery Linux VM has "nicer" fonts than the standard VM,
You might also want to check last code published in trunk.
Nicolas
2010/3/22 Eliot Miranda :
>
>
> On Mon, Mar 22, 2010 at 2:25 PM, Stéphane Ducasse
> wrote:
>>
>> eliot
>>
>> Your changes fixed some of the problems. Now I tried to fix the test
>> testAnalogousCodeTo in MethodPropertiesTest and
On Mon, Mar 22, 2010 at 2:25 PM, Stéphane Ducasse wrote:
> eliot
>
> Your changes fixed some of the problems. Now I tried to fix the test
> testAnalogousCodeTo in MethodPropertiesTest and
> the expression returns false.
>
> (#zork->'hello') analogousCodeTo: (#zork->'hello') -> false
>
> (#zork->
not sure that it does not introduce side effect but
Association>>isLiteral
^ self key isLiteral and: [self value isLiteral]
Fix the problem.
stef
On Mar 22, 2010, at 10:25 PM, Stéphane Ducasse wrote:
> eliot
>
> Your changes fixed some of the problems. Now I tried to fix the test
>
eliot
Your changes fixed some of the problems. Now I tried to fix the test
testAnalogousCodeTo in MethodPropertiesTest and
the expression returns false.
(#zork->'hello') analogousCodeTo: (#zork->'hello') -> false
(#zork->'hello') = (#zork->'hello') -> true
Stef
On Mar 22, 2010, at 6:20 PM,
On Mar 22, 2010, at 9:33 PM, stephane ducasse wrote:
> hi martin
>
> marcus and me integrated your fixes. Marcus should send a nice update mail.
done.
Marcus
--
Marcus Denker -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.
#11284
==
Hashed collection performance improvement, phase 4 of 4.
Changes identityHash to cover most of the positive SmallInteger range, and uses
good prime table sizes. This makes large hashed collections much faster, and
does not penalize the small ones.
Targeted at Pharo Core 1.1-112
#11283
==
Hashed collection performance improvement, phase 3 of 4.
Changes identityHash to cover most of the positive SmallInteger range, and uses
good prime table sizes. This makes large hashed collections much faster, and
does not penalize the small ones.
Targeted at Pharo Core 1.1-1128
#11282
==
Hashed collection performance improvement, phase 2 of 4.
Changes identityHash to cover most of the positive SmallInteger range, and uses
good prime table sizes. This makes large hashed collections much faster, and
does not penalize the small ones.
Targeted at Pharo Core 1.1-1128
#11281
--
Changes identityHash to cover most of the positive SmallInteger range, and uses
good prime table sizes. This makes large hashed collections much faster, and
does not penalize the small ones.
Targeted at Pharo Core 1.1-11280
Load the slice for each phase in order. Allow maybe
On Mon, Mar 22, 2010 at 9:22 PM, Bryce Kampjes wrote:
> On Thu, 2010-03-11 at 10:28 +0100, Mariano Martinez Peck wrote:
> > Both really interesting posts. Now...Some people reported that the
> > Exupery Linux VM has "nicer" fonts than the standard VM, even if both
> > use true type.
> > Then Bryce
hi martin
marcus and me integrated your fixes. Marcus should send a nice update mail.
Thanks again.
Stef (from my bed, got a nice virus from my smallest boy).
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.
On Thu, 2010-03-11 at 10:28 +0100, Mariano Martinez Peck wrote:
> Both really interesting posts. Now...Some people reported that the
> Exupery Linux VM has "nicer" fonts than the standard VM, even if both
> use true type.
> Then Bryce Kampjes said in the mailing list:
>
> "If it's font related the
Dale,
Another project that Citezen might need is Rio. It looks like Damien has been
busy. The ConfigurationOfCitezen is in the repository. For fun, I tried
Gofer project load:'Citezen'
and get an error "No versions matching version (latest)" I am not sure whether
this is something that I
Chris,
Understood, but somebody created what I thought was a correct patch to add
something to the workspace menu to do it, and it would be a shame to lose it.
Bill
-Original Message-
From: pharo-project-boun...@lists.gforge.inria.fr
[mailto:pharo-project-boun...@lists.gforge.inria.fr
Hi Mariano,
I worked on a similar problem for a new code profiler. Spy is a
framework for easily performing program execution analysis.
A short tutorial, screenshots, and some examples are available on:
http://www.moosetechnology.org/tools/Spy
If you're working in that direction, I would be d
Bill,
Looks like ConfgurationOfCitezen does need required projects added (I am
willing to help the maintainers - drop me a line).
Perhaps the configs aren't ready for prime time and that's why they have not
been added to MetacelloRepository.
You can add repositories to your own GoferProject:
Hi Bill, I think you can just create a new file in the file-list, cut
and paste your WS into it, save again..
On Mon, Mar 22, 2010 at 1:16 PM, Schwab,Wilhelm K wrote:
> Hello all,
>
> Some time ago, there was (I thought) a patch for saving workspace text to a
> file; I had hoped to find that in
Hello all,
Some time ago, there was (I thought) a patch for saving workspace text to a
file; I had hoped to find that in 1.0, but it is not in RC3 that I can find.
The first thing I did was load the Loader extensions to Gofer. It installed as
expected. I have not looked into the code, but tri
> 1) For a generic approach to method wrappers, which of those two ways would
> you use ? should I care about notifying, adding to localSelectors, etc?
> Or at is just temporal, I don't care ?
> which are the pros and cons you see with each alternative ?
I used #at:put: because we put-back the i
Oops. Find attached.
2010/3/22 Cyrille Delaunay
> try in a Pharo-1.0-10515-rc3 image :
>
> |set|
> set := Set new.
> Collection withAllSubclasses do: [:aClass |
> set addAll: aClass methods
> ].
>
> It will raise an exception telling: "MessageNotUnderstood:
> ByteSymbol>>analogousC
Hi folks. I was reading the PBE chapter about reflection where it talks a
little about Method Wrappers. Then, I took a look at TestCoverage
implementation.
After that, I took a look at
http://www.squeaksource.com/ObjectsAsMethodsWrap
The main difference between both approaches are:
TestCoverage
11287
-
Issue 2136: Smalltalk and SmalltalkImage
--
Marcus Denker -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin
11286
-
Issue 2179: Tweak from nicolas in sync Pharo and Squeak
Issue 2181: CompiledMethod >>getSourceFor: selector in: class
Issue 2173: MC browser selection
Issue 2186: Adding some methods to the WorldMenu for deprecation
Issue 2142: isInMemory should be removed.
--
Marc
11285
-
- Issue 2180: Move MetaObjectTools from core to PharoDev
- Issue 2165: CleanUp unused packages
--
Marcus Denker -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.
___
Pharo-project mailing list
Pharo-project@
good!
Stef
On Mar 22, 2010, at 2:59 PM, Adrian Lienhard wrote:
> My plan is to extract ImageSegments into an external package and maintain it
> there. Since I will probably not be able to make the class swapping work,
> this part of image segments will be dropped.
>
> If you start with removi
https://gforge.inria.fr/frs/download.php/26693/PharoCore-1.1-11284-UNSTABLE.zip
--
Marcus Denker -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforg
My plan is to extract ImageSegments into an external package and maintain it
there. Since I will probably not be able to make the class swapping work, this
part of image segments will be dropped.
If you start with removing #isInMemory, thats fine with me. I can do the rest
later.
Cheers,
Adria
Thanks cyrille!
Stef
On Mar 22, 2010, at 2:33 PM, Cyrille Delaunay wrote:
> try in a Pharo-1.0-10515-rc3 image :
>
> |set|
> set := Set new.
> Collection withAllSubclasses do: [:aClass |
> set addAll: aClass methods
> ].
>
> It will raise an exception telling: "MessageNotUnderstood
so do we remove imageSegments support?
Stef
The reason why the #isInmemory checks are there at all is the following:
-> they used imageSegements (and before, the ObjectOut stuff) to swap
out objecs to disk
-> Now if you access the class, it is loaded again.
This is cool to see a bold guy like that pushing that :)
Keep pushing mariano.
Stef
On Mar 22, 2010, at 12:19 AM, Michael Rueger wrote:
> On 3/21/10 4:07 PM, Mariano Martinez Peck wrote:
>
>> Hi Michael. Let me see if I understood.
>>
>> - In PharoCore I remove InputEventSensor >> processMenuE
try in a Pharo-1.0-10515-rc3 image :
|set|
set := Set new.
Collection withAllSubclasses do: [:aClass |
set addAll: aClass methods
].
It will raise an exception telling: "MessageNotUnderstood:
ByteSymbol>>analogousCodeTo:".
Indeed, in the code of CompiledMethod >> = , the message
'
Janko Mivšek wrote:
>
> Hi Geert,
>
>> Why a private discussion and/or voting? Isn't the whole point of GSoC to
>> engage the entire Smalltalk community?
>
> Smalltalk GSoC Mentors mailing list is actually visible to others, just
> that it is created in Slovenian and now I can't change the la
Hi Geert,
On 22. 03. 2010 09:04, Geert Claes wrote:
> Mariano Martinez Peck wrote:
>>
>> I am not sure but I think it is a private mailing list where mentors will
>> be able to discuss and vote.
>> Anyway, I will ask Janko just in case I am wrong.
> Why a private discussion and/or voting? Isn't
>> If there is one-click images for Pharo, it might be easier for newbies.
>>
>>
> There is, but experimental:
>
> look in https://gforge.inria.fr/frs/?group_id=1299
> "One-Click Experiments"
>
> Adrian offered him self also to do a new one for 1.0
Did I? I think that was Marcus :). But anyway
On Mar 21, 2010, at 23:46 , Marcus Denker wrote:
>
> On Mar 21, 2010, at 11:18 PM, Stéphane Ducasse wrote:
>>>
>>> The reason why the #isInmemory checks are there at all is the following:
>>>
>>> -> they used imageSegements (and before, the ObjectOut stuff) to swap
>>> out objecs to disk
On Mon, Mar 22, 2010 at 9:32 AM, Serge Stinckwich <
serge.stinckw...@gmail.com> wrote:
> 2010/3/22 laurent laffont :
> > OK, so the One Click image is really important. Nevertheless, I think
> there
> > should be a mean to quickly understand the distinction between VM and
> image,
> > that you can
2010/3/22 laurent laffont :
> OK, so the One Click image is really important. Nevertheless, I think there
> should be a mean to quickly understand the distinction between VM and image,
> that you can have several images. (The concept of image is new for a lot of
> people :), and it was for me 1 ye
On Mar 21, 2010, at 23:18 , Stéphane Ducasse wrote:
>
> On Mar 21, 2010, at 10:59 PM, Marcus Denker wrote:
>
>>
>> On Mar 21, 2010, at 10:51 PM, Stéphane Ducasse wrote:
>>
>> Well... it is needed for the swapping out of classes. If we remove
>> #isInMemory, we should also remove the
OK, so the One Click image is really important. Nevertheless, I think there
should be a mean to quickly understand the distinction between VM and image,
that you can have several images. (The concept of image is new for a lot of
people :), and it was for me 1 year and a half ago. It takes some ti
Mariano Martinez Peck wrote:
>
> I am not sure but I think it is a private mailing list where mentors will
> be able to discuss and vote.
> Anyway, I will ask Janko just in case I am wrong.
>
Why a private discussion and/or voting? Isn't the whole point of GSoC to
engage the entire Smalltalk
On Mon, Mar 22, 2010 at 8:51 AM, Serge Stinckwich <
serge.stinckw...@gmail.com> wrote:
> 2010/3/22 laurent laffont :
> > Hi,
> > last saturday I have organized a Pharo workshop in Annecy. 6 people out
> of 9
> > discovered Pharo & Smalltalk.
> > A first point to understand for newcommers is that y
On Mon, Mar 22, 2010 at 8:47 AM, Geert Claes wrote:
>
>
> Mariano Martinez Peck wrote:
> >
> > ...
> > We created a mailing list for all the mentors. If you are mentor, you
> > should be there. If you are not, please contact us.
> > ...
> >
>
> Where can I find this mailing list so I can add it to
2010/3/22 laurent laffont :
> Hi,
> last saturday I have organized a Pharo workshop in Annecy. 6 people out of 9
> discovered Pharo & Smalltalk.
> A first point to understand for newcommers is that you need:
> - the VM for your platform
> - the Pharo image
> - open the image with the VM.
> So maybe
Hi,
last saturday I have organized a Pharo workshop in Annecy. 6 people out of 9
discovered Pharo & Smalltalk.
A first point to understand for newcommers is that you need:
- the VM for your platform
- the Pharo image
- open the image with the VM.
So maybe you should put as big sized text at the t
Mariano Martinez Peck wrote:
>
> ...
> We created a mailing list for all the mentors. If you are mentor, you
> should be there. If you are not, please contact us.
> ...
>
Where can I find this mailing list so I can add it to the other mailing
lists on Nabble if you like?
--
View this message
51 matches
Mail list logo
