2 ms·
This is more or less the structure I followed with this testing framework: https://github.com/hitchdev/hitchstory https://github.com/hitchdev/hitchstory The wh
by pydry 6y ago
This is more or less the structure I followed with this testing framework: https://github.com/hitchdev/hitchstory https://github.com/hitchdev/hitchstory
The whole idea being that you don't want the story to be turing complete (there are no loops or conditionals with a story), but the code that executes it needs to be turing complete.
- bonestormii_ 6y agoRight, and it's not like it's ground breaking thinking here. It's just a matter of some personal restraint on your part to say, "No, I will not turn python into an interpreter for some disgusting yaml-based language." Everyone agrees we hate this, until one day it's us who is dreaming it up, and we just can't resist! There should be no concept of "flow of execution", except for maybe expansion of previously declared variables just so you can do something like concatenating two lines together. Otherwise, the lack of logical operations will make even that unnecessary.
- pydry 6y agoWell, knowing when the flexibility of turing complete language is required and when the simplicity of non-turing complete declarative language is required and where to draw the line between them is often pretty hard. This is why we get YAML based languages that edge towards turing completeness with conditionals and loops and ugly templating hacks. Mostly people get it wrong. I got it wrong several times when creating two earlier versions of that framework.