More SendMessage issues.

[Barabajagal]

$25 for certification from an ISO compliant certification system. They're fully accredited, used by many companies as a certification method. If you want to take a look, go to ExpertRating.com. If you don't want to believe they're a true form of certification, then whatever.

[FrOzeN]

You paid $25 for a certificate showing you know how to program in a deprecated language? What a total waste of money.

Essentially, VB6 is a language written in almost pseudo code allowing for RAD compared to what was previously available. I assume the reasoning behind allowing "Option Explicit" to be toggled on/off is that they wanted people to just type in code for what they wanted the program to do, and get it working with as little effort as possible. Though, it had it's huge fallback that all undeclared variables become Variants which requires VB6 to give them extra handling whilst being parsed around, and often lead to giving incorrect output. Not using Option Explicit for compiling a program of any importance is very stupid.

The idea behind dollar sign ($) and others to be used to declare variable types was probably to add a short-hand way of typing. However, it too is generally not used as the signs are also used when forcing certain built-in VB6 functions to return a value as a certain varible type (such as Mid$() returning a String, opposed to Mid() returning a Variant).

[Tazo]

okk since vb is so crappy, let's assume im doing this in c++. now what is the problem?

[topaz]

The use of $ probably derived from Perl

[Grok]

You think it's ok for a language to allow the coder to call variables that don't exist? srsly?


You're just as dumb as I thought you were when you put "I Am Not What I Am - iago from Shakesphere". lol @ phonetically spelling your words like a third grader

it is not a "bad feature", it's a "remnant". I'm not saying it's not useless nowadays, that statement just says it wasn't written as a new feature.

lol @ calling it a remnant. Perhaps there's a reason why it's a remnant instead of present in other languages? Give up. It's worthless and there's no reason for it to be there; I don't if you paid $20 for a piece of paper that says you're a Certified VB6 Interface Coding Professional. You admitted to it's worthlessness, and still you maintain the defense that it's still useful. Give up, you're a loser

Damn topaz, you've been busy getting in people's faces.  These two each add 15 days to your ban, bringing it to 45 days.

Go take a chill pill and learn to be part of a community.  You're smart, you should want to be helpful and not such a negative person.  If that's not your choice, well, good luck in whatever you do, but take it elsewhere.

[Barabajagal]

The use of $ probably derived from Perl

The BASIC language series has been around much longer than Perl. Perl's been around since 87, whereas BASIC was designed in 63. It's always used $ as a string definition.

[Mystical]

oh boy, to see what a computer looked like in 63 haha.. what would you even program in 63? a calculater? take your desktop comp around with u to cacluate things? =)

gezz if grok finds all of topaz's other post BOOM, he/shes gunna be banned for the rest of the year ahha

[Barabajagal]

Back then, PCs didn't exist. there were Mainframes, terminals, and timesharing. Computers had useful purposes, like bank databases, complex math calculations, and other more practical uses. BASIC was designed originally as a way for students to be introduced into the Programming world. Eventually, they realized if they kept the same Syntax, and improved the features, they could make programming a lot easier.

[LCSBSSRHXXX]

Yes, because I don't remember something, and state that I don't remember it, I must be a liar. How wonderful your logic is. Of course there's no point declaring variables that don't exist. Removal of Option Explicit lets you save time by NOT declaring variables and using them anyway. When converted to assembly and compiled to an EXE, the converter adds the declarations automatically.

Not using Option Explicit is a bad choice, when Option Explicit isn't being used I'm pretty sure it treats all undeclared variables as Variants and a value declared as a Variant is more memory intensive and not friendly.  Also not declaring variables can lead to problems when trying to read over code to find a problem in the application.  If I'm incorrect about what I just said please let me know, I have not programmed in a long time, but I'm pretty sure that what I said is true.

Lazy is not an excuse, variables should always be declared.

[Barabajagal]

As long as you add the correct symbol to the end of the variable name, it should be defined as the correct type. It wouldn't surprise me if Microsoft dropped that standard, though . Yes, Option Explicit is good. Yes, you should always declare your variables. But it's still an option, and if you use it right, it makes things easier (as long as you don't screw up the spelling), which is what the BASIC series goal is.

[Mystical]

well as far as i know option explicit i've used as a tool to let me know what i've had undeclared. If you don't use it, and you have undeclared variables, then they are automaticly variants. it shouldn't really matter if you have it in your class, form, module if everthing in it is declared? I think it's a good programming habit to be the first thing you have in your classes. to my knowlegde of compiling, you can't compile if you have Option Explicit in a module with variables undeclared. thus acts like vb helper =) and maybe i jsust read your messages wrong, to much typing, and you just wasted a good minuate or 2 reading what i just wrote, thanks! =)

[Warrior]

As long as you add the correct symbol to the end of the variable name, it should be defined as the correct type. It wouldn't surprise me if Microsoft dropped that standard, though . Yes, Option Explicit is good. Yes, you should always declare your variables. But it's still an option, and if you use it right, it makes things easier (as long as you don't screw up the spelling), which is what the BASIC series goal is.

If I crash my car it makes it easier for me to get hurt. Is that a good thing? No.

Not using Option Explicit makes something easier..it makes it easier to have bugs in your code. No one is a perfect programmers, programmers are humans.

[Barabajagal]

Actually, it's more of seatbelt. It makes getting in and out of your car harder (if you're not used to it), and when you screw up, it's there to save you.... wow, i like that metaphor..

[Warrior]

You missed the entire point. Don't you get it? Nothing that makes the compiler assume anything about something as crucial as variables can be good. Just because something is easy doesn't make it good. If it's bad in the first place, it defeats the purpose of it being easy.

[Barabajagal]

...actually, I don't think you're reading my postings correctly. I'm completely against not declaring variables in today's languages, and my seatbelt = option explicit example seems like a perfect metaphor (except that it's not illegal not to use it).