Teaching a class of novices, it's not surprising that someone tried "Collection
new". What was surprising is that this got the VM is a loop of some kind, with
emergency stack dumps and so on.
Here is my reply:
> On 30 Jan 2012, at 01:18 , Xingzhi Harry Pan wrote:
>
>> ...it's pretty innocent
On 30 January 2012 19:31, Andrew P. Black wrote:
>
>
> But I don't understand the root cause. Printing eventually sends do:,
> which is self subclassResponsibility. Why don't we get a clean failure?
>
>Andrew
>
When an error occurs during error handling (which includes printing) it is
n
Hmm, is this really right? I'm used to seeing "Error in printString ..."
On 30 Jan 2012, at 11:12 , Milan Mimica wrote:
>
>
> On 30 January 2012 19:31, Andrew P. Black wrote:
>
> But I don't understand the root cause. Printing eventually sends do:, which
> is self subclassResponsibility.
On Jan 30, 2012, at 4:30 PM, Andrew P. Black wrote:
> Hmm, is this really right? I'm used to seeing "Error in printString ..."
>
Wasn't that a bug we already fixed? In 1.4 I can do Collection new and I get
the subclass responsibility...
And I thought we back-ported the fix to 1.3, too.
Nee
On Jan 30, 2012, at 4:35 PM, Marcus Denker wrote:
>
> On Jan 30, 2012, at 4:30 PM, Andrew P. Black wrote:
>
>> Hmm, is this really right? I'm used to seeing "Error in printString ..."
>>
>
> Wasn't that a bug we already fixed? In 1.4 I can do Collection new and I get
> the subclass respons
t the vm.
Bill
From: pharo-project-boun...@lists.gforge.inria.fr
[pharo-project-boun...@lists.gforge.inria.fr] on behalf of Andrew P. Black
[bl...@cs.pdx.edu]
Sent: Monday, January 30, 2012 1:31 PM
To: Pharo Project
Subject: [Pharo-project] Collection
In general why is there not a catch all for Stack Overflow and infinite
loops.
Thats very annoying for newbie.. and infact gives a bad feel to using
Pharo. The image they are working for say 3-4 hours and the crash just
pushes them out of all the code they are working on with.. small as it
maybe..
On Mon, Jan 30, 2012 at 9:18 PM, S Krish
wrote:
> In general why is there not a catch all for Stack Overflow and infinite
> loops.
There is, low space (and user interrupt for flat infinite loops). But the
low space interrupt machinery is easily broken. It is difficult to test,
and an increasin
On Tue, Jan 31, 2012 at 3:40 PM, Eliot Miranda wrote:
>
> On Mon, Jan 30, 2012 at 9:18 PM, S Krish <
> krishnamachari.sudha...@gmail.com> wrote:
>
>> In general why is there not a catch all for Stack Overflow and infinite
>> loops.
>
>
> There is, low space (and user interrupt for flat infinite lo
On 31 January 2012 06:18, S Krish wrote:
> In general why is there not a catch all for Stack Overflow and infinite
> loops.
In general, you just press Alt+., several times.
--
Milan Mimica
http://sparklet.sf.net
Does not work all the time in busy loops.. it continues with other
debugger windows.
Would love it if Alt . completely stops all other processing.. some
kind of master interrupt...
On 2/1/12, Milan Mimica wrote:
> On 31 January 2012 06:18, S Krish wrote:
>
>> In general why is there not a catch
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
17 matches
Mail list logo
