Oh well. I did say it was just my vote.
I don't regard the addition of attributes.pm as bloat, nor would I feel qualified to use the phrase "I don't have a clue what I'm doing" in connection with a user who had difficulty figuring out why pp didn't work. I don't think users should have to figure out why pp doesn't work. It seems to me that being able to type 'pp' and just have it work without really having to know how or why is a desirable goal. If adding the module attributes.pm to the mix helps to achieve that then that seems a good thing to me. I know I use tools and technologies every day without having the first clue how they actually work - so maybe I'm in the "haven't got a clue" section. Perhaps we could have a "--miss-out-essential-bits-flag" for use by the cognoscenti which would allow them to bring the full and mighty weight of their knowledge to bear, and have 'pp' just produce working execs for the rest of us? Mark Eric Wilhelm wrote: > # from Mark Dootson > # on Monday 25 June 2007 10:09 am: > >> I think it might be best to add attributes.pm by default as an >> implicitly required module. > > I have to disagree. The compiler will tell you if you need it or not. > Adding it "in case someone might need it" seems too capable of creating > bloat. > > Perhaps a --bloat flag? At least a --nobloat option please. > > It really comes down to whether pp/M::SD intend to support "I know what > I'm doing" usage or "I don't have a clue what I'm doing" usage. Both > have their uses, but I prefer to not let ease-of-learning interfere > with power and ease-of-use. > > --Eric
