Sure, but depending on the recursion, that technique will vary from "inelegant" to "maddeningly brittle".
It seems like going pretty far just to avoid recursion, unless you're in a resource-constrained domain.
There is nothing brittle about it, you push values to the stack instead of passing them to a function (which just pushes them to the call stack). It actually ends up being far less brittle in practice because it is much easier to deal with edge cases and errors. You can break out of a loop much easier than returning different values and having those bubble up.
You can just take the variables you are passing to each recursive call, put them in a struct, and make a stack of those structs.