Function definition

[Ivan Čukić]

> have to tag functions that can potentially blow the stack, otherwise face a
> warning.

> possible downside: it's often quite OK to have non-tail-recursive functions
> if you *know* the number of iterations is small (e.g. due to a known to be
> small data set) and that might lead to a more functions than desired being
> marked this way?

This makes sense +1

> [1] or for extra niftiness: mutually recursive .. perhaps even N-cycle
> multiple recursion for a reason N

This is a bit more involved, but yes, it could be a nifty feature.


Cheerio,
Ivan


KDE, ivan.cukic at kde.org, http://ivan.fomentgroup.org/ 
gpg key id: 850B6F76, keyserver.pgp.com