Hmm... well, the hacky calendar way wasn't really easy (and maybe not even possible) in my situation, but managed to solve this with replacing the code
vars->exposed = .ExposedInterface();
with this: vars->exposed = ((program) "ExposedInterface.pike")();
solved it.. can't really see why it should make any difference though... ? (as with the inherit in my Proxy.pike, also needs to inherit from the string "ServerObject.pike" to work)...
I've run across this before, that I have to delay program resolvment until runtime, and not during compile time... is this a sign of me doing something wrong, or is this a shortcoming of the pike compiler?
//K
Kaos wrote:
Mirar @ Pike developers forum wrote:
You should absolutely positively not look at the Calendar to see how things are supposed to be.
The Calendar module has recursive dependencies that needs to be untangled before it can load.
(Time needs Timezone to be loaded, and Timezone needs Time to be loaded to be able to calculate the timezones for the calendar time. This is untangled by making a special instance of Time that is without timezones, namely the Calendar.ISO_UTC instance. Or so.)
I guess that it's the way it's not supposed to be.. but if I can get things to work by applying some master()->resolv during module "boot" (tagging on to the _module_value access to `[]) I'm going for it.. but I'll definitely bring up the discussion about what isn't working as expected, but as it is now I can do nothing since my app won't even run.. :(
//K