[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Visual Basic and case-sensivity

From: Steve Greenland
Subject: Re: Visual Basic and case-sensivity
Date: Thu, 13 Dec 2001 10:06:11 -0600
User-agent: Mutt/1.2.5i

On Thu, Dec 13, 2001 at 04:15:33PM +0100, ?yvind Idland wrote:
> We use CVS in our organisation, and its an incdredible tool.
> However, we have a couple of Visual Basic programmers here.
> If one, for example changes a function-name from FOOBar to Foobar,
> the VB IDE parses _every_ single for FOOBar and changes the case to Foobar.
> (unbelivable, but its true.. )

It's worse than that. The project files contain fullpath references
to the DLL's used by the project. Even if you require that all your
developers use consistent paths, Windows seems to sometimes resolve
them all uppercase, sometimes mixed case. Even if this doesn't lead
to conflicts (and it often does), it means that your project files
often show that they're modified, even though the developer hasn't done
anything except check it out and opened the project. Thanks Mr. Bill.

Oh, a solution for the function renaming? "Don't do that".


reply via email to

[Prev in Thread] Current Thread [Next in Thread]