RE: Re: Visual Studio.Net and Subversion - Will this make it into a release?
From: Leeuw van der, Tim <tim.leeuwvander_at_nl.unisys.com>
Date: 2004-03-08 15:29:21 CET
Hi,
Not that I have any code to contribute to solving the problem, but using a method-private static variable leaves you without any 'outside' control over the cached value. There's no way to invalidate the cached value, or to provide a non-default value *other* that by setting an environment variable (command-line parameter, stored preference). For long-running programs, there's no way to pick up changes to the environment variable.
I can't think of any non-ugly 'instant solution'; and of course this is just the first step -- nothing stopping anyone from adding more proper interfaces later. I do realize that for those who need some control, this is already miles better than 'only at compile time'! Better to make many small steps into the right direction then to get there in 1 big step. Just wanted to point out some limitations of this method.
-----Original Message-----
Garrett Rooney wrote:
--- beware, untested code ahead ---
// svn_wc.h
// adm_files.c
// cache value in a static to prevent multiple calls to getenv()
assert(adm_subdir);
Uli
---------------------------------------------------------------------
---------------------------------------------------------------------
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.