Dag Sverre Seljebotn wrote:
> If one decides to change the temp allocation flow altogether, I have 
> another proposal:

*And*, if that is done, there might be a lot of monotone but crucial 
work (tear it down and build it up), so we better have a coordinated 
coding session with IRC chat. I can put in two or three hours tomorrow.

I am a bit scared of the prospect of implementing my own proposal 
though. Before changing the entire flow we need to schedule developer 
time so it doesn't get out of hand (Robert has some scary stories to 
tell about the SAGE "coercion" remake :-) arguably this change is 
isolated to 4000 lines in ExprNodes.py).

The drawback with my proposal is that it doesn't seem easy to be 
backwards compatible, it needs tearing out and rebuilding stuff. Then 
again, without all the restrictions that are there on the current temp 
system (i.e. must allocate during analysis, trying to reuse temps in 
ways that should be much easier in a parent-manages-temp scheme) the 
problem seems to become a lot smaller than the problem the current 
complicated code has to solve.

(I'm putting the string constant stuff on hold, this is more important.)

-- 
Dag Sverre
_______________________________________________
Cython-dev mailing list
[email protected]
http://codespeak.net/mailman/listinfo/cython-dev

Reply via email to