Jakob Hirsch wrote: > But now there's a different problem: I rewrote the code to use the btree > functions. Easy to handle while they are in memory, but what to do when > they go to disk? Dumping is easy, but when reading in, tree_insertnode > has to be called for every variable, which is expensive with all its > rebalancing etc. As far as I can see, there are three possible solutions: ....... > 2. Write information about the tree into the spool file (like the > existing tree_write does). This an incompatible change, once again, > but it's easy to write a small script to rewrite the spool files into > the old format, should somebody have a need for that.
As the format will be changing anyway, I don't see a problem here. Nico -- ## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
