From: Alex B. <en...@tu...> - 2001-10-02 17:39:26
|
> we have different xml files, translated to php and used only during make > (i.e. the language or image repository). These files are compiled to php and > stored in the build tree (regarding to the docs). First, because I can see the need potentially for admin tools that would need access to those arrays. Second, because I don't want to incur the overhead of re-parsing a set of _big_ xml files on every make - reading native php structures is _much_ faster and I want make to be as fast as possible. The first reason is a bit tenuous, but the second is solid :) > We use them only during make and the php structures are not used on runtime > (or are they?). So why creating them as files? Isn't it enough to parse the > xml files and build the array internally, doing the replacement work and > write the outputfiles? Why mess up the build tree with those files? > > Ok, it's not pain in the a** to have them there and the only advantage I see > is for debugging purposes. How would there be an advantage for debugging if those files we not in the tree? You could be 100% certain that they were not being accessed, unless you specifically wrote a module to access them :) _a |