| Author |
Message |
|
Hugh Lyn
#1 / 7
|
 Automatic capitalization of variable names, type names, subs and functions Automatic capitalization has been problematic for my team, which
shares projects through SourceSafe. Often, opening a project and
changing a single line in a .cls file causes changes to capitalization
throughout the file. THis makes it very hard to find the signficant
changes using SourceSafe's file differencing tools. Anyone else have
this problem? Any solutions?
Thanks,
Hugh {*filter*}
|
| Tue, 17 Aug 2004 01:16:31 GMT |
|
 |
|
Eric
#2 / 7
|
Automatic capitalization of variable names, type names, subs and functions You do have OPTION EXPLICIT in every single source module, don't you? It is
NOT the default in VB. Lack of OPTION EXPLICIT can cause this.
Quote: > Automatic capitalization has been problematic for my team, which > shares projects through SourceSafe. Often, opening a project and > changing a single line in a .cls file causes changes to capitalization > throughout the file. THis makes it very hard to find the signficant > changes using SourceSafe's file differencing tools. Anyone else have > this problem? Any solutions? > Thanks,
> Hugh {*filter*}
|
| Tue, 17 Aug 2004 01:22:44 GMT |
|
|
|
Lee Silve
#3 / 7
|
Automatic capitalization of variable names, type names, subs and functions Hugh:
Quote: > Automatic capitalization has been problematic for my team, which
> shares projects through SourceSafe. Often, opening a project and
> changing a single line in a .cls file causes changes to capitalization
> throughout the file. THis makes it very hard to find the signficant
> changes using SourceSafe's file differencing tools. Anyone else have
> this problem? Any solutions?
We too use SS for our source-control and have the same problem -- if
someone defines a local variable with different capitalization than a
Method/Property/etc. in a referenced Class, the reference is given the
case of the local variable.
Eric's suggestion about Option Explicit has no bearing on this -- all
our files have Option Explicit. The only solution we found was
self-discipline in naming our variables -- they should maintain the Case
of existing Methods/Properties/etc.
At check-in time, if the Diff shows that there differences in Case, the
check-in is Cancelled, the differences corrected and the file checked-in
again.
--
// Lee
|
| Tue, 17 Aug 2004 02:00:34 GMT |
|
|
|
Ivan Demkovitc
#4 / 7
|
Automatic capitalization of variable names, type names, subs and functions When you check for difference you can check box "Ignore case"
It is fine with VB
Quote: > Automatic capitalization has been problematic for my team, which > shares projects through SourceSafe. Often, opening a project and > changing a single line in a .cls file causes changes to capitalization > throughout the file. THis makes it very hard to find the signficant > changes using SourceSafe's file differencing tools. Anyone else have > this problem? Any solutions? > Thanks,
> Hugh {*filter*}
|
| Tue, 17 Aug 2004 02:34:56 GMT |
|
|
|
Joe
#5 / 7
|
Automatic capitalization of variable names, type names, subs and functions Quote:
> Automatic capitalization has been problematic for my team, which
> shares projects through SourceSafe. Often, opening a project and
> changing a single line in a .cls file causes changes to capitalization
> throughout the file. THis makes it very hard to find the signficant
> changes using SourceSafe's file differencing tools. Anyone else have
> this problem? Any solutions?
Bleah... Can SourceSlay be told to do case-sensitive comparisons on
some files but do "binary" comparisons on others? Then segregate all
embedded strings out into files tagged for case-sensitive comparisons,
since you'd want to catch "Save changes?" turning into "sAVE cHANGES?"
Of course, auto-craps isn't a whole hell of a lot better now than it
was back in VB3. Didn't the auto-craps guy talk to the Shift-F2 guy?
--
Joe Foster <mailto:jlfoster%40znet.com> Sign the Check! <http://www.xenu.net/>
WARNING: I cannot be held responsible for the above They're coming to
because my cats have apparently learned to type. take me away, ha ha!
|
| Tue, 17 Aug 2004 02:34:58 GMT |
|
|
|
Steve Austi
#6 / 7
|
Automatic capitalization of variable names, type names, subs and functions Quote: > You do have OPTION EXPLICIT in every single source module, don't you? It is
> NOT the default in VB. Lack of OPTION EXPLICIT can cause this.
It *IS* the default for VB5 Pro...
|
| Tue, 17 Aug 2004 05:16:11 GMT |
|
|
|
Jan Hy
#7 / 7
|
Automatic capitalization of variable names, type names, subs and functions
released on 28 Feb 2002 09:16:31 -0800 bearing the following
fruit:
Quote: >Automatic capitalization has been problematic for my team, which
>shares projects through SourceSafe. Often, opening a project and
>changing a single line in a .cls file causes changes to capitalization
>throughout the file. THis makes it very hard to find the signficant
>changes using SourceSafe's file differencing tools. Anyone else have
>this problem? Any solutions?
This can be a useful feature if used correctly, we make it a
standard that all variables have a capital letter eg
Dim strName as string
J
|
| Fri, 20 Aug 2004 17:26:20 GMT |
|
| |
