Hi Tom, is it quiet in here or is my email on the fritz?
Modules were weird and unclear abstractions in the old VB days that
irritated and confused me. They still do, so whenever I make a new VB
project I delete the Module and I create classes. I'm probably biased here
because I come from a
to VB.NET.
_
Ian Thomas
Victoria Park, Western Australia
_
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Greg Keogh
Sent: Sunday, 6 June 2010 3:19 PM
To: 'ozDotNet'
Subject: RE: Vb.net Modules or classes
Hi Tom, is it quiet in here
.
|-Original Message-
|From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-
|boun...@ozdotnet.com] On Behalf Of Ian Thomas
|Sent: Sunday, 6 June 2010 6:53 PM
|To: 'ozDotNet'
|Subject: RE: Vb.net Modules or classes
|
|Greg
|
|Over the years, there have been some discussions on this, eg Joel Spolksky
, Western Australia
-Original Message-
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com]
On Behalf Of Bill McCarthy
Sent: Sunday, 6 June 2010 5:14 PM
To: 'ozDotNet'
Subject: RE: Vb.net Modules or classes
Hi Greg, Ian, all
As Ian says a Module is a Shared
Chaps, I think we've answered Tom's question in a way, eventually, I hope.
He was suspicious of using Modules, and you've confirmed my suspicions that
Modules are aliases for static classes that don't need to be qualified. No
other .NET compliant language I know of hides what's going on underneath
Cheers guys, very helpful.
On Sun, Jun 6, 2010 at 8:19 PM, Greg Keogh g...@mira.net wrote:
Aha! Here’s the statement that sums it all up with legal clarity:
http://msdn.microsoft.com/en-us/library/7825002w(v=VS.80).aspx
*This means that variables in a standard module are effectively
Gday dotnetters,
Ever since I switched to vb.net i find im using Modules more and more,
rarely creating classes, particularly at the entry point into a few utility
console apps im working on. This definitely feels wrong, is it just bad
design? Should i be learning OO design again?
As an
