Re: Global Const vs Public Const

On Mon, 11 Sep 2006 17:28:48 +1000, "Michael C" <nospam@xxxxxxxxxx>
wrote:
in <#UZvINX1GHA.4796@xxxxxxxxxxxxxxxxxxxx>

"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


That's fairly humorous considering that the .NET languages/platform may
portend the EOL of the vendor itself.

---
Stefan Berglund
.

Relevant Pages

  • Re: Global Const vs Public Const
    ... only for the new meaning that Global doesn't already cover. ... an eol language there's no point avoiding the eol keywords :-) ... At least as far as development tools go. ...
    (microsoft.public.vb.general.discussion)
  • Re: Stupid regex problem
    ... On vrijdag 07 april 2006 01:15 Stefan Ram wrote: ... It depends on the meaning of »the EOL would be irrelevant«. ... In the described problem the EOL is simply irrelevant. ...
    (comp.lang.java.programmer)
Loading