Why does this compile?

[duh]

Hello, If I have

----------------------------

Public Sub Test(i As Integer)

End Sub

Load()

Test("Hello")

End Sub

-----------------


Why does the program compile with no errors? Shouldnt vb see that the argument passed to Test is not an integer?

Thanks

[phinds]

clearly the code as you posted it will not compile as you have two end subs with only one sub start. Post your actual code.

[duh]

My question is, why does the code compile.
Shouldn't the compiler see that you are passing a
string as a parameter instead of an integer.


Public Sub Test(i As Integer)

End Sub

Private Sub Form_Load()

Test("Hello")

End Sub

[M Owen]

That applies only when you pass a variable (i.e. a variable of type string)... You are passing a pointer to a local stack and VB renders the value into an integer ...

[duh]

Hi,

I changed



Test("Hello") To

Dim t As String
t = "Hello"

Test(t)


It still compiles.

[Confucius]

I don't think the compiler cares what you are passing a function. All it cares about is IF you are passing one or not and whether or not it requires one.

This is also true in your code.
Try a numeric variable that your are trying to use as alpha and create a calculation with it but don't run it to get a runtime error. Instead, just compile it and you'll see what I mean.

HTH

[duh]

Hi,

I see that it doesnt care what type the argument is. I want to know if this is something that can be changed by choosing some sort of option in VB.

For example, what is the point of having types in the arguments of a function if they are not used to help the coder avoid passing incorrect things to functions before it is run.

Can someone give answer this.

[M Owen]

You have option explicit turned on?

[Confucius]

You have to remember how a function works.
Until you run it and pass it something then how is it going to know that what you are passing is valid or not? It's just code waiting for an action. There is no cross-referencing on arguments passed because on compile, you're not passing anything to it.

I have to ask this though: Why are you compiling something you haven't tested to begin with?

[duh]

I have option exlicit.

I come from a c++ background.

The reason you want this to happen confus is because it makes more reliable and less buggy code.

What if I had the following code.

------------------

Public Enum Colour
Red = 1
Blue = 2
End Enum

Public Sub Test(col As Colour)


End Sub

Public Sub Form_Load()

Test(4)

End Sub

---------------

The compiler should see that 4 is not of type, Colour and it
should not compile. It makes the debugging easier.

My simple question is, does anyone know if vb can do this type of checking.






-----------------

[Confucius]

There's a price to pay for ease of programming when using VB and you just found one of many in comparison to C++

Interpretive languages like VB, REXX, etc. have many flaws in comparison with more rigid languages like C++

C++ is not as forgiving as VB. It's hard to crash a user's PC with VB code unless you really screwed up badly. No so with C++

Not to mention the learning curb

[duh]

I wonder then what is the point of using enums in the
arguments of a function

[But_Why]

Originally posted by duh
My simple question is, does anyone know if vb can do this type of checking.

The reason you want this to happen confus is because it makes more reliable and less buggy code.

Confucius is right, VB can test this. Run the program? It would make no sense to write a program, then not test it in the IDE and expect to have no bugs...

[But_Why]

Ooops i jumped the gun, didn't see your last replys...

[Rizwan Rafique]

Oops!
Mine works
I mean it doesnt compile on my computer