An answer to an experienced Perl programmer can be more terse, but a newbie would benefit far more from a detailed explanation.

Why are you now splitting how he (or anyone) should answer? It takes enough time to answer, and now someone should evaluate the questioners experience before answering? How do you know what someone will benefit from? I don't always think that a long detailed answer is best for a newbie. Why? Because teaching them how to teach themselves can be more valuable that showing them the answer. Why are you picking on merlyn for this? Do you read others answers on this site? The range from "perldoc something" to long, overly detailed explinations. Everyone has their own style, which may change daily or hourly depending on mood or how busy one is. The important thing is that people participate. If you don't like someone short, terse answer.. noone is stopping you from expounding on it.

Cheers,
KM

Why are you now splitting how he (or anyone) should answer?

I guess I'm naively going by what works best for me. Should I couch all of my comments like that? "My answer is based on what works for me."

Why are you picking on merlyn for this?

Interestingly, this all started at my disagreement with merlyn's method of tracking down personality voters. That is what I am picking on merlyn for. The following disagreements have been resolved privately by merlyn and I, although I plan to make that conversation public, since merlyn and I feel that it might help others.

Do you read others answers on this site?

Surprisingly enough, I do. I have seen the range of answers. I have added to conversations where I saw appropriate. I have not added in general to merlyn's terse comments because quite often the area is one I am not familiar with.

Guildenstern
Negaterd character class uber alles!

Surprisingly enough, I do. I have seen the range of answers. I have added to conversations where I saw appropriate. I have not added in general to merlyn's terse comments because quite often the area is one I am not familiar with.

So there's an interesting possible explanation that popped into my head.

Perhaps you just get frustrated because I don't say enough when it's something you're not familiar with.

Perhaps you object to the way I answer only one fact in the right direction when I think it'll be the fact that helps the original poster along.

That would explain your upset. You want me to provide the complete bridge, not just point the way to the building materials.

-- Randal L. Schwartz, Perl hacker