Markus Schiltknecht wrote:
Humpf... I've just added a 'path::status cached_status;' to any_path,
with an additional which returns that or gets the status.
The problem now is, that this routine needs to *write* the status into
any_path.cached_status, requiring that the any_path in question is not
const, but writable. That breaks a whole lot of any_path & const xy
routines. And I'm unsure if its good to remove all those consts.
Another way to do it would be, implementing all that caching inside the
platform dependent 'get_path_status'. But on second thought, this isn't
that simple as well, because we don't know about the lifetime of the
underlying any_path class there.
In a long-lived monotone instance, caching may actually be dangerous.
Maybe generalized status caching isn't such a good idea...
-- Ulf
_______________________________________________
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel
