5 kyu
Esolang: Ticker
343 of 560user2514386
Loading description...
Interpreters
Strings
Arrays
Esoteric Languages
View
This comment has been reported as {{ abuseKindText }}.
Show
This comment has been hidden. You can view it now .
This comment can not be viewed.
- |
- Reply
- Edit
- View Solution
- Expand 1 Reply Expand {{ comments?.length }} replies
- Collapse
- Spoiler
- Remove
- Remove comment & replies
- Report
{{ fetchSolutionsError }}
-
-
Your rendered github-flavored markdown will appear here.
-
Label this discussion...
-
No Label
Keep the comment unlabeled if none of the below applies.
-
Issue
Use the issue label when reporting problems with the kata.
Be sure to explain the problem clearly and include the steps to reproduce. -
Suggestion
Use the suggestion label if you have feedback on how this kata can be improved.
-
Question
Use the question label if you have questions and/or need help solving the kata.
Don't forget to mention the language you're using, and mark as having spoiler if you include your solution.
-
No Label
- Cancel
Commenting is not allowed on this discussion
You cannot view this solution
There is no solution to show
Please sign in or sign up to leave a comment.
python new test framework
Approved by someone.
This kata is pure garbage, I propose to retire it.
Julia translation
This comment has been hidden.
Fixed tests are not testing for 255+1 = 0 and 0-1 = 255
fun kata, 10/10
C translation here!!!
My solution works 100% for all the set tests, but fails on about 98% of the random tests. Anyone with any suggestions?
Updating this comment with an 'Issue' marker.
language?
Had the same issue. In my case it was because I did not check for cases when pointer became negative.
This kata desperately needs a set of more complicated fixed tests.
This isn't actionable.
FYI in PHP you don't need to wrap the cell data since
chr()
will do that for you!Swift translation kumited. Please review and approve if satisfactory.
You should clearly state that this only applies if the current cell is within bounds. It's very difficult to debug the random test cases that have 10k commands each when specific requirements are omitted.
Do you mean that a new cell with the value of 0 should be added to the end of the cells that are in memory? For example, if the data array's last cell with an integer value is
20
, but the pointer is currently set at50
, does that mean the new cell added should be at index21
or51
?If the cell data for index
50
is set to0
by the/
command, and the next command is!
, does the newly added cell go to51
, or to the last contiguous integer-value cell in memmory? To reiterate, if cells21
through49
are not in memory, but the pointer is set to50
, is the added cell supposed to be set at21
or51
?For the
!
command, new cell should be added at index21
. For other commands, if the pointer is out of memory bounds, assume that the cell value is0
but if you use the+
or-
commands, the imaginary cell value still stays0
.That still doesn't answer his second question. Since / is neither + or - then it would set the value of a cell that has not been created through !. If the data pointer was set to 50 for / does the next ! then fill 51 or 21?.
Ruby Translation Kumited! Please accept ;D
tyvm for that translation! Ruby ftw <3
Description is unclear, inconsistent and you keep calling decrement "increment -1".
Have you seen the recommendations at the top? I put them there for a reason.
Ahh, i see. So to completely make sense of the description, one needs to do all the related tasks in order?
No, I just put them there for users to understand the point of esolangs and what this kata is asking. @donaldsebleung does a great job of explaining how to make an esolang interpreter.
Concept is one thing, my complaint is for inconsistent description. Task descriptions should be stand alone thing which covers everything you need to know to solve the task. And you should refer to things the same way you defined them on top.
Example: "!" -> add data cell, but then you refer to it as "add to memory". We shouldn't have to decifer descriptions to solve the kata, just sayin.
This comment has been hidden.
PHP Translation Kumited - please accept :D
Accepted.
Add test for out of bounds with
<
,test.assert_equals(interpreter('<<<*'), chr(0))
JavaScript Translation Kumited - please accept :D
UPDATE: Apologies, I somehow broke my original translation (think it might be a Codewars issue). Please approve this one instead :)
Great Kata on Esolangs, loved it, keep up the good work :D <3
Just a few suggestions:
-
has not been tested despite being mentioned in the Kata Description. It would be great to see at least 1 to 2 tests that include this command.0
and that the!
command is required to expand the data tape by 1 cell to the right. Perhaps you could specify in your Kata description how the interpreter should respond when the data tape isn't expanded sufficiently and the selector goes out of bounds (and possibly add a few test cases for that)?Thank you for your suggestion, I added random tests and fixed the initial tests.