Too many nested GOSUBS error

[Fairlight]

Four score and seven years--eh, screw that!
At about Tue, Sep 19, 2006 at 10:16:34AM -0700,
Tyler blabbed on about:
> (rant:  when I asked about why the limit at all, much less so low, I
> was told that recursion wasn't a real programmer's technique; it's
> only useful for irrelevant things like calculating fibonacci
> sequences.  filePro doesn't need to support anything so useless -  16
> nested gosubs should be enough for anybody!  Me, I use recursion often
> in other programming languages, as it is very handy and often makes
> for clean and elegant solutions.  Particularly when you need to
> navigate parent-child relationships between data that don't have a
> fixed number of descendants)

Obviously whoever told you that doesn't do much filesystem or data
structure traversal with anything of a dynamic nature.  But since hardly
anything in filePro is actually dynamic, of course they don't.  You can't
even set up a hash, much less a linked list, array of arrays or array refs,
etc., so in some ways it's of limited value.  That's no excuse for poor
implementation of gosub/return, however.

I can't believe someone actually -said- it's not a real programmer's
technique.  That's patently absurd.  Recursion is one of -the- most
efficient reuses of existing code there is.  Of all the excuses I've heard
over the years, that's probably in the top 10.  Arguably, this would belong
in the joke list alongside, "Real programmers don't eat quiche," if they
hadn't actually been serious when they fed you the line about recursion.

I feel your pain.

mark->