in reply to Re^7: Capturing regex from map
in thread Capturing regex from map

Understanding either or both does not make the OP's code a shining beacon of clarity,

If you understand it, how can it possibly be unclear?

This is exactly the same ridiculous argument as is proffered here so often.

Yes. Of course, *I* understand it, but other people might not, so therefore, it is not "a beacon of clarity".

And if you do not understand it; just say that. Then we can point you to the documentation; and perhaps offer further examples, or a break down of why and how it works, to help you reach the understanding you are lacking.

Do not advocate the dumbing down of other peoples code, simply because you don't understand it; or you fear that others might not.

The key to understanding is not pretending the (in this case, hardly) complicated stuff doesn't exist; it is education.

Don't seek to cover it up, or hide in in a box labeled "wizards only"; explain it.

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.

Replies are listed 'Best First'.
Re^9: Capturing regex from map
by Anonymous Monk on Sep 16, 2013 at 06:06 UTC
    I'm saying that it can, for the OP's case, be trivially made easier to understand. It did take me a few minutes' head-scratching to see what it did, and it surprised me that the community's response about its clarity was positive.

    In my case, I don't use the list-returning properties of regexps often, nor do I expect map to subtract from or add to the amount of elements in the array. If I need to kill elements, I generally leave a hint such as () inside the map block.

    I do not view this behaviour as dumbing down code at all, but just saving people's heads from excess scratching, that they are able to instantly see what that line does. The Perl community does have a reputation of abstruse write-only code, you know, and I think this line would be a perfect example of excess terseness the community is infamous for. (For the record, I hate Java for its dumb verbosity. Middle grounds exist, too.)