[Top][All Lists]

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

RE: Visual Basic and case-sensivity

From: Eric Boman
Subject: RE: Visual Basic and case-sensivity
Date: Thu, 13 Dec 2001 13:48:37 -0600

We create a script to go through the VB files and change the references to the 
proper case before doing any CVS operations.


-----Original Message-----
From:   Steve Greenland [SMTP:address@hidden
Sent:   Thursday, December 13, 2001 12:38 PM
To:     address@hidden
Subject:        Re: Visual Basic and case-sensivity

On Thu, Dec 13, 2001 at 03:39:04PM +0000, Kenneth Loafman wrote:
> Slightly off topic... does that mean that VB is case-insensitive, or is
> this a case of the IDE trying to "help"?

The VB language is not case-sensitive -- "FOOBAR" is the same identifier
as "foobar". But the IDE likes to help you keep things consistent. This
seems nice, except that it sometimes changes what you just typed to be
consistent with the rest of the instances, and sometimes changes all the
other instances to be consistent with what you just typed (I'm sure it's
not completely random, but it sometimes seemed like it).

> As to CVS, those changes would be a conflict since most languages are
> case-sensitive (i.e. FooBar for the global, foobar for local copy).

CVS don't know nuth'n 'bout no languages. Text is text. It's the job of
the compiler or interpeter or whatever to determine. The conflicts come
when someone else has edited a line referencing FooBar.

And I'm not sure I'd say "most languages are case-sensitive". C and
C-derived and C-inspired langauges, sure. But there's a lot of Fortran
and Cobol out there...not to mention BASIC.


Info-cvs mailing list

reply via email to

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