So keeping from being "runaway" just means ensuring that my recursive function indeed will unwind (stop recursing) as intended? Piece of cake... ;) Thanks for the tips.
peternilsson42 writes: > "crasypantz" <[EMAIL PROTECTED]> wrote: >> >> I think I've seen in the past (maybe not here, but probably) much >> debate regarding the good, the bad, and the ugly of programming >> using recursion. I don't know that I ever saw a final verdict. > > You're not likely to ever see one. > >> I am curious if the argument changes when talking about the >> embedded world. > > Nope. Same arguments, just different parameters. ;-) > >> I have a project and the most straightforward and efficient >> (as I see it at least) solution is to use recursion. A friend >> said he'd heard 'recursion equals bad' in the embedded >> environment. > > No. Runaway recursion equals bad in any environment, embedded > or otherwise. > >> I know there are many savvy minds here so if there is a good >> argument why recursion should or needs to be avoided then >> please could someone offer a little insight with valid reasons >> instead of me just going with what someone 'heard'? > > It doesn't need to be avoided, it needs to be constrained. > Of course, avoidence is one form of constraint. :-) > > -- > Peter >
