Re: Global Const vs Public Const
- From: "Michael C" <nospam@xxxxxxxxxx>
- Date: Wed, 13 Sep 2006 09:14:03 +1000
"Bob O`Bob" <filterbob@xxxxxxxxxxxxxxx> wrote in message
news:esdxVUp1GHA.4972@xxxxxxxxxxxxxxxxxxxxxxx
Seems to me more a fault of vb. Public should be used everywhere and
behave the same.
That's ludicrous because different behaviors are *needed*
Actually no you're statement is ludicrous. There is absolutely no reason at
all the behaviour should be any different.
It's not much of an issue anyway as public variables in a module
should be extremely rare. I only declare instances of classes as public
in a module anyway. I just checked my app which is quite large and there
are 2 public vars in a module which I didn't add. Surely something that
has such wide scope should be private and wrapped in a property anyway.
That's just an opinion.
It's fairly well accepted that global variables should be minimised.
Michael
.
- References:
- Re: Global Const vs Public Const
- From: Jeff Johnson
- Re: Global Const vs Public Const
- From: Bob Butler
- Re: Global Const vs Public Const
- From: Michael C
- Re: Global Const vs Public Const
- From: Stefan Berglund
- Re: Global Const vs Public Const
- From: Bob Butler
- Re: Global Const vs Public Const
- From: Michael C
- Re: Global Const vs Public Const
- From: Ralph
- Re: Global Const vs Public Const
- From: Michael C
- Re: Global Const vs Public Const
- From: Bob O`Bob
- Re: Global Const vs Public Const
- Prev by Date: Re: best way to detect a hole in a control array
- Next by Date: Collision detection
- Previous by thread: Re: Global Const vs Public Const
- Next by thread: Re: Global Const vs Public Const
- Index(es):
Relevant Pages
|