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.
In reply to Re: (Guildenstern) Re: Re: But I'm not like that at all!
in thread Method calling question... by satchboost
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>