Well, since the OP's post started with arrays rather than strings your golf is cheating slightly ;-)
However, if the problem comes from the real world I think the odds are better than even that the OP started with strings and split them into arrays in order to do the comparison. In that scenario your golf is fine, though anything other than "snippet" dna strings are unlikely to fit on the command line!
| [reply] |
| [reply] |
$ perl -pale '$_^=$F[1];$_=y/\0//'
ATCGTCGAGCG ACGTCCTGTCG
4
| [reply] [d/l] |
Do you all know of a good place I can study or learn about these short/compact functions? Is it called perl golf? What is perl golf? | [reply] |
Do you all know of a good place I can study or learn about these short/compact functions? Is it called perl golf? What is perl golf?
Re^3: Golf code in perl (Context)
And no, please don't use "golfed" code for any other purpose than to play golf. It's simply unmaintainable in that form, write-only code in its purest form. Prefer writing longer, readable code that you (or any other maintainer) will still understand in half a year, a year, or five years. If you resort to "dirty tricks" (like string xor plus counting NUL bytes), add a comment that explains how the trick works and the requirements for that trick (e.g. strings must only contain ACGT, all upper case, both the same length, etc). Don't make your future self invent a time machine to come back and severely hurt you for the mess you will have written.
Alexander
--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
| [reply] |