> Building type filtering directly into the core however locks you to The 
> One Right approach, while different transforms will have different 
> needs. I cannot see any performance benefits either.
>   
Also, how would you build type filtering into the core at all, if not by 
using transforms to implement it? Certainly not by hard-wiring it into 
the current code-processing-in-methods-in-nodes?

As I said earlier, I'm a strong believer of Transform.py simply being 
about creating a more modular and maintainble compiler core, not about 
building a plugin framework. Transforms and plugins are two conceptually 
different things, the former being a necessity for the latter.

I'll calm down now :-) Thanks for raising the point, I'm curious to hear 
your thoughts...

-- 
Dag Sverre

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

Reply via email to