all these people reinventing the wheel :)

🍴

It's ok but description has been unified so you need to update (or fork) or we'll have a merge conflict.

• Description cannot be approved, recent changes from related record must be merged first
• Language Version is invalid for c

Simple regex replace and implementing a calculator are not novel kata ideas.

The description says ""h((el)l)o" becomes "h(l(el))o"". I think it was supossed to be ""h((el)l)o" becomes "h(l(le))o"", or am I wrong?

Wow, this one is crazy, it took me one hour. Thanks, it was original and challenging.

you could add "()" to the edge cases for C, I had first written a solution that didnt handle this and stll passed

Hi @dmercertaylor - there have been a couple of issues raised about the C translation of this kata not matching the description. Any chance you could take a look at them?

Done now. It seems a lot longer than the others!

Plenty of them feature things I haven't yet learned, though, so I'm not going to beat myself up too badly.

Thankyou. I'm not printing anything... I will think about where this comes from.

Edit: it turns out I did leave a testing print inside a recursive function. Oops!

But still timed out. Back to the drawing board.

Check if this FAQ is of any help.

I have a solution which passes all the initial tests, but when I hit Attempt it throws up this:

STDERR
Max Buffer Size Reached (1.5 MiB)

I am not at all experienced, and am finding it very difficult to find anything in the randomised case output that tells me where I am going wrong.

Any ideas please, anyone?

Yes, it is intended that you account for these cases, as they are included in the edge case tests (although not in the normal sample tests). I have updated the description to reflect that.

It would be nice if the description clarified the relationship between cmp and subroutines (i.e. should subroutines affect the value of the parent "most recent cmp" or get their own). I don't believe this case is tested either way, though.