In fact radio.weblog.init() was a red-herring. Although that's where I
was getting the stack overflow exception it's not the cause. I seem to
get it at a particular point in the script regardless of what code is
Sometimes the error is:
Stack overflow: error info stack (when it occurs on a
Stack overflow: local info stack (when it occurs on a
Stack overflow: source info stack (when it occurs while I
am in debug mode)
What puzzles me is that the stack seems to blow at about 200 levels
deep, but I've pushed it much farther than that in testing. Is there
some kind of maximum size of all stack information at work here?
From: Dave Winer [mailto:dave@...
Sent: 26 October 2002 17:48
Subject: Re: [radio-dev] Recursion & radio.weblog.init()
1. No, strictly speaking it's not safe to cache it, but in practical
terms it is. It's a future-safety issue. We put the init routine there
to make transitions easy if we ever have more than one weblog per Radio
installation. But with categories, that seems unlikely. But, better safe
than sorry. But, we break the rule ourselves in the Prefs system.
There's no hard and fast rule here.
2. As far as I know radio.weblog.init does not call itself. Do you know
of a way it can?