Re: globals?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



It may seem like that to you but that isn't what the message is. Computer
languages form "contracts" between the developer and the machine. Legal
contracts use specific words to reduce ambiguity and programming contracts
must similarly choose systems which reduce ambiguity.

If we extend your example then every individual in every neighborhood is
free to interpret anything you type in any way they choose. You post here
confident that "reasonable" interpretations of your words will result in the
meaning you intended. If 10 people in Leeds think you should use the word
"OneUpton" instead of Singleton are you likely to say "I see your point" and
start doing that? No of course not and if only VB.Net uses UCase() why
should the world change particularly since VB.Net has ToUpper() and VB
developers use it all the time?

You can find well-written modules to be anything you wish them to be and you
should use them if you want. I'm stating that the other DotNet languages
don't have such modules and that putting UCase() into one isn't a great
example of their benefit. I'm also pointing out that most major companies
aren't "VB shops" they are companies that use VB along with other languages
to solve business problems. Things which tend to be language specific are a
detriment not an asset. The more different it is, the less likely it is to
be used.


"Cor Ligthert [MVP]" <notmyfirstname@xxxxxxxxx> wrote in message
news:eyBkXVhQHHA.1036@xxxxxxxxxxxxxxxxxxxxxxx
Tom,

As I read your message is it like as some people who wish that all
Americans are talking only true English. However that does not even exist,
every neighbourhoud in England has its own words.

By the way I find a good written module always nicer than those Singleton
and Static class approaches were almost nobody knows what is meant with
that, but as I see an approach to give the module to C languages.

And everbody seems forever to forget that the module has in Net private
members, which did not exist in VB before 2002.

Cor


.



Relevant Pages