Re: Pike/Roxen: clean start issue

I haven't taken the time at the moment to reproduce the problem and I seriously doubt if I can. Now that the error is spotted, the module only compiles now if the error is fixed. One thing I can say though, is that I've equipped every Roxen module with a creation time stamp because I had a gut feeling before that after reloading a module and it's related code Roxen didn't always use the latest version of the code (either correct or incorrect)

In Roxen, I've seen caching to sometimes be a bit to thorougly (editing files does not clear them in cache automatically). However a Roxen restart and /or Flush Cash from the admin interface always reloads them.

Persisten cash for modules, between Roxen starts, has never happend to me.