Ruby interpreter error on initital tutorial about yeetwords HOT 4 CLOSED

Oh gosh, thank you for alerting me to this error! I am looking into it. I have replicated your error on my system and can confirm we are looking at the same error.

I am trying to figure out with my code where the problem is.

from yeetwords.

Some good news and some bad news. The good news: I am on track for making a bug fix for this specific issue. Basically, I tried rewriting my function standard_write iteratively instead of recursively so as hopefully not to run out of stack space, and that change solved your specific problem. It's not up yet as a pull request because I need to tighten up the rewritten function a bit more, make sure other calls from elsewhere to that function go smoothly, and do more local testing first. But on a preliminary local test with your exact data as above, it works and produces 50000 words output. I'm hoping to have that specific item in as a pull request in the dev branch around 24h from now if there are no hiccups cropping up with that change and if I can complete the testing in that timeframe.

The bad news: If I change your novel.txt code to instead achieve the number of words via a LOOP command as shown below, then again we wind up with a stack level too deep error on ruby interpreter. Most likely, I'll have to also rewrite my loop_iterator function iteratively :( which is recursive despite its name! I'll raise this one as a separate issue.

LOOP 50000W
WRITE mysentences wfolder
LOOPEND

Interestingly, not all instances of LOOP 50000W have problems in YeetWords - I have one in another repository that is working fine, see https://github.com/verachell/Limericks-NaNoGenMo-2021

One bug fix at a time though - I'll go ahead first with the bug fix specific to the issue you raised.

from yeetwords.

from yeetwords.

Thank you so much for bringing this problem with the WRITE command to my attention! I have now fixed this problem, tested the solution, and the changes have been merged into the main branch. The 1.1.1 release reflects this change. Let me know if you have any questions.

I'm going to tackle the similar issue #4 next (LOOP command).

from yeetwords.