May be you should raise the question in the vm mailing-list.
It would be a really great feature.
Stef
Le 8/6/16 à 21:33, Esteban A. Maringolo a écrit :
2016-06-08 6:29 GMT-03:00 Sven Van Caekenberghe :
On 08 Jun 2016, at 11:24, Jan Vrany wrote:
Not
2016-06-08 6:29 GMT-03:00 Sven Van Caekenberghe :
>
>> On 08 Jun 2016, at 11:24, Jan Vrany wrote:
>> Not entirely true :-) There are smalltalks out there that detect such stack
>> growth and do the same as CL,
>> throw a (resumable) exception. Super-handy.
On Wed, Jun 08, 2016 at 11:11:13AM +0200, Sven Van Caekenberghe wrote:
>
> > On 08 Jun 2016, at 10:40, Henrik Johansen
> > wrote:
> >
> >
> >> On 04 Jun 2016, at 9:13 , stepharo wrote:
> >>
> >>
> >>
> >> Le 3/6/16 ?? 19:16, Esteban A.
> On 08 Jun 2016, at 11:24, Jan Vrany wrote:
>
>
>
>>
>> IMHO, all Pharo beginner tutorials should start by showing off Cmd - dot
>> (or Alt - dot, on Win / Linux).
>>
>> Not just because it's cool, but because it's necessary :)
>>
>> Cheers,
>> Henry
>>
>>
IMHO, all Pharo beginner tutorials should start by showing off Cmd
- dot (or Alt - dot, on Win / Linux).
Not just because it's cool, but because it's necessary :)
Cheers,
Henry
Very true.
Yet, and I have already mentioned this years ago, it is technically
totally possible to
> On 08 Jun 2016, at 10:40, Henrik Johansen
> wrote:
>
>
>> On 04 Jun 2016, at 9:13 , stepharo wrote:
>>
>>
>>
>> Le 3/6/16 à 19:16, Esteban A. Maringolo a écrit :
>>> Regarding the first part of your email, about UI lockups, it is almost
> On 04 Jun 2016, at 9:13 , stepharo wrote:
>
>
>
> Le 3/6/16 à 19:16, Esteban A. Maringolo a écrit :
>> Regarding the first part of your email, about UI lockups, it is almost
>> unavoidable, because in Pharo almost everything happens in the main
>> thread, as you pointed
Le 3/6/16 à 19:16, Esteban A. Maringolo a écrit :
Regarding the first part of your email, about UI lockups, it is almost
unavoidable, because in Pharo almost everything happens in the main
thread, as you pointed out.
Yes. This is all my point.
When only UI events should happen there,
and
Regarding the first part of your email, about UI lockups, it is almost
unavoidable, because in Pharo almost everything happens in the main
thread, as you pointed out. When only UI events should happen there,
and have background processes/async tasks for computation and I/O that
updates the UI by
the mooc is a mine for Pharo bugs...
In the video at 6:12, we have a new method sending the new message. I've
made similar mistakes and Pharo does lock up, but then the operating
system (Windows 10) kills the Pharo VM. (Or perhaps there's a bug in
Pharo itself which just crashes the whole
10 matches
Mail list logo