Well I don't know about the latest.NET incarnation but yes, VB is case insensitive as far as variable naming goes. In fact in the IDE if you enter "strdouble" after a "Dim strDouble as String" statement then "strdouble" is turned into "strDouble". The same thing applies to keywords (all of which have the leading letter capitalized.) If you enter "next ndx" then it will be turned into "Next ndx" when you press enter.
As regards variable initialization, Visual Basic automatically initializes variables. Numeric types are zero, strings are "", variants are "Empty", booleans are "False".
When I was working as a programmer I fixed a lot of problems caused by the previous programmers.
Many of them were caused by their making assumptions about the way the data would be presented to the program i.e. database records will always be sequentially numbered 1,2,3,4,5,6,...
These assumptions came about because the previous programmers would always generate the test records in the same way every time and never took into account that the user could do things like delete records 1,3,4 and 5.
Dumb things were done like hardcoding loops iterating from 1 to N over the database records. This would work well as long as the records were in fact numbered from 1 to N. Feed in records that weren't numbered from 1 to N and things quit working immediately. I was quite surprised that no one before me had ever caught this.
I ran into this kind of thing so often it wasn't even funny.
Another problem that I had was that the programmer just prior to me had a penchant for using IIf statements a mile long. Nesting them was also considered to be great fun. Putting all the code he could in one statement made for much better code in this guy's mind.
Seeing as a lot of this code didn't work right and had zero comments, I wound up breaking almost everyone one of these sick, twisted puppies up into separate lines/statements so I could try to figure out what the heck he was thinking when he coded them.
I used to use IIf statements myself but now I still have an aversion to using them after seeing how they can be misused.
I've tended to write much cleaner, readable, commented code after having experienced working with other people's cluttered handiwork.
If I feel like e-mailing my friend that "his midnight plutonium shipment to pier 27 will be delayed until 1:30am" just for the heck of it, can I? Or will the feds knock my door down within 10 minutes?
Do this often enough and it'll be like the little boy who cried wolf. They'll be like "Who's it from? Oh, fuck, it's HIM again. Just put him in the spam filter."
The navy wants gliders with internal actuators because they have no flaps or propellers, no lubricant, and one already exists that could "fly" under the Pacific from Seattle to Tokyo on a penlight battery!
This must be a penlight battery for the Jolly Green Giant's penlight.
Slashdot Mirror
I recognize that. That is from the short story "A !Tangled Web" by Joe Haldeman.
Well I don't know about the latest .NET incarnation but yes, VB is case insensitive as far as variable naming goes. In fact in the IDE if you enter "strdouble" after a "Dim strDouble as String" statement then "strdouble" is turned into "strDouble". The same thing applies to keywords (all of which have the leading letter capitalized.) If you enter "next ndx" then it will be turned into "Next ndx" when you press enter.
As regards variable initialization, Visual Basic automatically initializes variables. Numeric types are zero, strings are "", variants are "Empty", booleans are "False".
When I was working as a programmer I fixed a lot of problems caused by the previous programmers.
Many of them were caused by their making assumptions about the way the data would be presented to the program i.e. database records will always be sequentially numbered 1,2,3,4,5,6,...
These assumptions came about because the previous programmers would always generate the test records in the same way every time and never took into account that the user could do things like delete records 1,3,4 and 5.
Dumb things were done like hardcoding loops iterating from 1 to N over the database records. This would work well as long as the records were in fact numbered from 1 to N. Feed in records that weren't numbered from 1 to N and things quit working immediately. I was quite surprised that no one before me had ever caught this.
I ran into this kind of thing so often it wasn't even funny.
Another problem that I had was that the programmer just prior to me had a penchant for using IIf statements a mile long. Nesting them was also considered to be great fun. Putting all the code he could in one statement made for much better code in this guy's mind.
Seeing as a lot of this code didn't work right and had zero comments, I wound up breaking almost everyone one of these sick, twisted puppies up into separate lines/statements so I could try to figure out what the heck he was thinking when he coded them.
I used to use IIf statements myself but now I still have an aversion to using them after seeing how they can be misused.
I've tended to write much cleaner, readable, commented code after having experienced working with other people's cluttered handiwork.
My father tells the story of a guy working at an auto assembly plant who took home an entire car -- piece by piece!
That's a Johnny Cash song. It's called "One Piece at a Time"
Lyrics to "Once Piece at a Time"
By my calculations based on Seti's stats from the last 24 hours the 500 millionth result will be reached in 3.67 days.
I've been around people with Craftsman tools that broke and who were going to throw them away.
I'd say "Hey, don't throw that out. It's got a lifetime warranty. Just walk into Sears with it and they'll give you a new one. No receipt needed."
They'd be like "I don't have the time. I'll just replace it with a Snap-On when the man comes around."
I'd then take the broken tool, toss it in the trunk and then the next time I went to Sears I'd take it to hardware and have it replaced.
I've gotten a 1/2 inch ratchet, 2 adjustable wrenches and numerous box-end wrenches and sockets and screwdrivers this way.
If I feel like e-mailing my friend that "his midnight plutonium shipment to pier 27 will be delayed until 1:30am" just for the heck of it, can I? Or will the feds knock my door down within 10 minutes?
Do this often enough and it'll be like the little boy who cried wolf. They'll be like "Who's it from? Oh, fuck, it's HIM again. Just put him in the spam filter."
I find it highly unlikely that anyone in their right mind would consider such a move.
What? You expect someone (Mark Forman) who strongly resembles Cletus the Slack Jawed Yokel to be in their right mind?
All the years of careful inbreeding make that unlikely.
The navy wants gliders with internal actuators because they have no flaps or propellers, no lubricant, and one already exists that could "fly" under the Pacific from Seattle to Tokyo on a penlight battery!
This must be a penlight battery for the Jolly Green Giant's penlight.
What's going to happen when you don't have an icon in your system tray and have no inkling that a foreign program is running on your PC?
What? You don't regularly monitor the processes running your system?
When I saw the previews of this movie I thought it was dumb. I may have to see it to see just how bad it is.