Smalltalk › Squeak › Squeak - Dev

Re: [Vm-dev] Re: pharo 4.0 Crashed in the VM thread again

‹ Previous Topic Next Topic ›
 
classic Classic list List threaded Threaded
♦
♦
 1 message Options
Nicolai Hess
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: [Vm-dev] Re: pharo 4.0 Crashed in the VM thread again

Nicolai Hess
Pharo or Squeak ?

In squeak, this stackframe / large stackframe bug was introduced some months ago by a change for the compiler but it is already fixed.
In pharo, we have a simliar bug (in pharos compiler (opal), not related to the change on the squeak compiler).
This is a bug that is known but not yet fixed
13854
frameSize calculated wrongly for #lineSegmentsDo: !



2015-08-09 18:39 GMT+02:00 tim Rowledge <[hidden email]>:

Sabine,
As a general rule of thumb, if a method is too long to see at a glance - in practice this means too long to fit on your screen - then it almost certainly needs splitting up. I have been forcibly reminded of this a lot recently due to having to decode insanely long Python routines; seriously - 1100 lines for a single function?

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Strange OpCodes: FSRA: Forms Skip and Run-Away
Free forum by Nabble Edit this page