Beta
Sparkle Interpreter
13Mihail-K
Loading description...
Parsing
Interpreters
Strings
Mathematics
Algorithms
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.
Since the author is inactive and that the kata description is lacking most of the important stuff about the lexer and other stuff, and the test suite is lacking random tests, I'm tempted to take this kata down (like actually "destroy" it from the edit panel as far as possible) and publish a fully revamped version, without the lexer (I don't see the point of this one, actually).
Opinions about that?
I don't think it's fair to destroy this one.
Make a new one. If it has random tests and no lexer, it won't be a duplicate.
ok, noted (I had other feedbacks pushing in the same direction on gitter. I'll just have to find the motivation... x) )
I'm toying with the idea of making this a Haskell and / or JavaScript project.
If I do I may also create a new kata instead, because I don't see the point of pre-including a lexer either.
If we stick to the language spec, we should arrive at the same kata, so either could be a translation instead of a new one.
You can't have a kumite in multiple languages, can you?
kumite: I don't know.
But if I do this new version, I'll (at least, I "plan to"... x/ ) add some other specs in additions (powers, maybe strings & mutliline strings, maybe right/left associativity of operators, push further the scopes managments, things like that) to make it more different (actually, to forbid the use of solutions here for the ogther one).
Just came across this again.
I guess my Lambda Calculus compiler pretty much is what that project would have been. Mainly because LC can encode just about anything ..
I just took a look at the existing solutions again, and turns out 4 out of 9 solves are using reflection/class patching to cheat the kata (and I just hardcoded the results because there are no random tests ;-)).
Something should be done to stop them ;-)
Needs random tests.
The tests are catching all
Throwables and printing their stack traces, which includes failed test assertions.This means we'll be drowned with output logs if we have failed tests.
8 completions and no ratings, which is amazing.
Could the Tokenizer's source code be made available? I'm trying to solve this in Python first and since it's not available i'm hand-writing my own.