> Are you saying that hardware is going to get more expensive? It's
> possible, but it's not the way to bet. At any rate, in
> countries where
> disk is expensive, bandwidth also tends to be expensive, or so I
> understand, so that doesn't really affect the tradeoff.
Internet bandwidth is expensive, not LAN bandwidth. Even in countries
where computer infrastructure is expensive, the office LAN is relatively
cheap, and lets face it, the vast majority of developers are likely
to be connected to a LAN, not a WAN.
> We already put a suffix on text-base filenames, so your "find" command
> should be unaffected. I'm not sure how cscope works.
cscope works on extension. Yes the directory structure I was looking
at was ancient. You can scratch that negative off the list.
> here is the fundamental problem with your solution:
>
> The WC code is already really hairy.
Feh ... you should see some of the crap I have to deal with here :)
Hairy code doesn't scare me. But I think it CAN be done realtively
simply. Granted I havent examined ALL of the wc code in detail. I
plan on doing that over the next few nights.
> * Anything which requires the WC code to behave differently, you'll
> have to find the resources for.
I volunteer.
> * Anything which requires the WC code to become more complicated (by
> giving it N different ways of operating) will probably get vetoed
before
> 1.0.
That'd be a pity if it can be demonstrated to work.
> I've been thinking that the wc library might want to go
> through a vtable
That makes sense but may be too destabalising for 1.0.
Kean
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 16 21:14:09 2002