Hi,
I was coding in
Pharo1.3
Latest update: #13315
By evaluating some tests again the emergency evaluator pop up (Pharo
doesn't like me lately :) ).
This time at least I figure that some elements i use in the tests do not
print properly:
so if you do
Collection new printString.
the image seems
On Mar 31, 2012, at 6:43 PM, Fabrizio Perin wrote:
> Hi,
> I was coding in
> Pharo1.3
> Latest update: #13315
>
13315 is very old. The current version is 13327... and your problem sounds like
something we fixed a long time ago.
> By evaluating some tests again the emergency evaluator pop up
On Mar 31, 2012, at 6:43 PM, Fabrizio Perin wrote:
> Hi,
> I was coding in
> Pharo1.3
> Latest update: #13315
>
> By evaluating some tests again the emergency evaluator pop up (Pharo doesn't
> like me lately :) ).
> This time at least I figure that some elements i use in the tests do not
> pr
>
> 13315 is very old. The current version is 13327... and your problem sounds
> like something we fixed a long time ago.
+1
>
>
>> By evaluating some tests again the emergency evaluator pop up (Pharo doesn't
>> like me lately :) ).
>> This time at least I figure that some elements i use in t
Hi,
As I wrote:
I don't know if those are suppose to be bugs or my inappropriate use of
Collection and SequenceableCollection. I just reported.
So thanks for all this info.
Cheers,
Fabrizio
2012/3/31 Stéphane Ducasse
>
> >
> > 13315 is very old. The current version is 13327... and your proble
it took us some time and you should not redefine class
class
^'class' asParser caseInsensitive trim
grgrgrgrg of course the system breaks if you return an object instead of a
class.
I sw now that you fix.
Stef
On Apr 1, 2012, at 8:58 AM, Fabrizio Perin wrote:
> Hi,
> As I wrote:
> I
