# from Roderich Schupp
# on Monday 25 June 2007 03:07 pm:
>...2212 bytes...
A little here + a little there + a little more = bloat. No, it's not
optimal as-is, but I don't think that makes a good excuse to make it
less so.
>Skim over recent posts to this list and you'll discover that pp is not
> regarded as a developer tool, but rather as a convenience thing.
> People just use it without
>having to think much about it (like perl itself) - which IMHO is good.
That might be the case. But I have to ask questions like: if we really
want it to "just work", why isn't --compile the default?
Of course, M::SD could try to detect attribute usage, but not without
reinventing the perl compiler or using PPI (maybe.)
Maybe pp needs to be broken into two tools? The more I try to tune my
own build process, the more I tend to think that it needs a sort of
timestamp + dependency-caching. Running pp without a lot of tuning on
a large project is *very* slow.
--Eric
--
"It works better if you plug it in!"
--Sattinger's Law
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
