This might be a silly question but....
I have not made much use of modules in recent years. I've been called on to
translate an old VB6 program to Dot Net 2.0. Aside from the sheer complexity
and lack of docs, there is one thing that caught my attention: The original
programmer made a great deal of use of modules in his DLLs. One element of
his style was to create class declarations in the module (Public x as Class1)
and then set x to reference the class in the class itself (x = Me).
Now I've whipped up a little test program and I know this still works but I
was just wondering how this measures up as acceptable (or should I say
'modern') programming style?
(It seems an innocent enough technique but given that the legacy program as
a whole is major spaghetti, I thought I'd ask for a second opinion.)