New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deduplicate - Caesar cipher + ROT13 + Atbash #203
Comments
Quite a bunch of kata, maybe someone has an idea for a better organization or categorization. My pick is: From Caesar kata, keep 3. for a couple of reasons (oldest, just as many translations when compared to the rest, most solutions). From Atbash kata, I think one should be enough, I don't think we need more. I like the 10. the most due to the parametrized alphabet. I don't like 11., but if you think that such a combined task is fine, we can keep it. To summarize, I'd vote to keep 3., 7., 10., and maybe 11. and retire the rest. |
From
From
From
From |
"Ceasar Cipher": vote for keep 2, retire the others |
From the
The rest seems logical to keep in |
Most people seem to agree to keep 2. or 3., 7., and 10. No one voted for the other ones, so I think we can get rid of them. |
Moved CoffeeScript translation from 6. to 7. |
From wiki list
Ceasar Cipher
step
which can be larger than alphabet size and needs to be modulo'd by users. Characters form outside of allowed alphabet should be passed through unmodified. Only encryption.step
which can be larger than alphabet size or less than 0 and needs to be modulo'd by users. Characters form outside of allowed alphabet should be passed through unmodified. Only encryption.[1, 26]
. Solution is a class with encryption and decryption ops.ROT13
Like Caesar, but shift is fixed to 13, and decryption is identical to encryption.
Atbash Cipher
Atbash is not exactly equivalent to Caesar cipher with a shift, but is often seen as equally dull as Caesar. Caesar and Atbash might, or might not, be seen as similar enough to keep only one, or both. It's one of the points to be discussed in this ticket.
Other
Conclusion
The text was updated successfully, but these errors were encountered: