> Tracing through perlio.c shows how much EVIL it is. All 80K > of it. I > simply have no words for this code. Extremely inefficient > and bloated, > doing enormous amount of work for trivial tasks - not even mentioning > how buggy it turns out to be! Apparently the principal task I've reported similar thoughts a couple of months ago - see attached message. Additionally, there are several places where local temporary variables assigned just to make further assignment less verbose. ("buf" in PerlIOStdio_read function is an example). IMHO while idea of perlio.c is good, and it allows cool things, it's implementation could be cleaned greatly. Best wishes, Vadim.Thread Previous | Thread Next