comment on

I look forward to reading your patch.

I didn't offer one.

On one hand you admit you don't know what the problem is, yet on the other you assert you know what you are talking about. Both can't be right.

Of course they can. (Look back for the phrase "unfortunately necessary supposition".)

if you understand the patches

Bingo!

But that only tells us the problem that you feel needs addressing and how you've chosen to tackle it.

It doesn't tell us how you think that scenario might come about; nor what other solutions have been considered.

But enough! We've descended below what is apparently the justifiable cut-off for the depth of a discussion (>10), and all we are doing is talking at each other, so let's stop here and see what time will tell us.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^12: 5.18.0 is available NOW! by BrowserUk
in thread 5.18.0 is available NOW! by Tux

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<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>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks