Re: Global Const vs Public Const

"Bob Butler" <tiredofit@xxxxxxxxxxx> wrote in message
news:umj7bvT1GHA.4648@xxxxxxxxxxxxxxxxxxxxxxx
"Public" therefore has 2 different meanings depending on where it is used
so
it makes sense to use Global when that's what you mean and Public only for
the new meaning that Global doesn't already cover.

"new hotness" is not always better as we have so painfully seen

Normally I would say this is a bad idea but I guess if you're using an eol
language there's no point avoiding the eol keywords :-)

Michael


.

Relevant Pages

  • Re: Global Const vs Public Const
    ... In a BAS code module the two have identical meaning; ... "new hotness" is not always better as we have so painfully seen ... using variants without explicit type casting. ... ambiguity to begin with. ...
    (microsoft.public.vb.general.discussion)
  • Re: Global Const vs Public Const
    ... Global is just for backwards compatibility. ... In a BAS code module the two have identical meaning; ... "new hotness" is not always better as we have so painfully seen ... using variants without explicit type casting. ...
    (microsoft.public.vb.general.discussion)
  • Re: Global Const vs Public Const
    ... Global is just for backwards compatibility. ... In a BAS code module the two have identical meaning; ... "new hotness" is not always better as we have so painfully seen ...
    (microsoft.public.vb.general.discussion)
  • Re: Global Const vs Public Const
    ... Global is just for backwards compatibility. ... In a BAS code module the two have identical meaning; ... "new hotness" is not always better as we have so painfully seen ...
    (microsoft.public.vb.general.discussion)
  • Re: Global Const vs Public Const
    ... Global is just for backwards compatibility. ... In a BAS code module the two have identical meaning; ... "new hotness" is not always better as we have so painfully seen ...
    (microsoft.public.vb.general.discussion)
Loading