30 Jan
2010
30 Jan
'10
11:56 a.m.
I wrote a small Gofer script (attached) which does
what I need except I was
surprised that class initializations appear to occur in the reverse order in
which the packages are loaded?
Yeah, that's annoying, but it is not the fault of Gofer. Monticello
(and for that matter also change-sets or file-ins) always executed
initializers in an arbitrary (alphabetical) order (or not at all, if
the code didn't change).
I could probably hack that the initializers of the packages would be
evaluated in the right order, but inside the package that would be
still random. So I don't know if this is worth the trouble?
For know, the issue you report is a bug in your package. You have to
write the initializers so that they work in any order.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch