Use of the CALL keyword

[sigid]

This is a general question regarding the use of the CALL keyword...

I'm not referning to external procs, but rather to internal or intrinsic procs.

I have read that the use of the keyword CALL is considered to be obsolete and to have detrimental effects on the operation of the application.

Does anyone have any specific insight as to whether this is right or wrong, and what these effects might be?

Simple minded Example:
Msgbox "OK"
vs
CALL Msgbox("OK")

[Hack]

I have not known Call to have a determental effect.

It is included with the language more for backward compatibility than practical use however.

[gavio]

Please check Call statement thread.

[penagate]

The difference is purely syntactic.

In VB6 calling a procedure without trapping its return value means you do not use the parentheses around the argument list.

MySub arg1, arg2
' vs.
ret = MyFunc(arg1, arg2)

Call allows you to call a Sub, or call a function without trapping its return value, and use the argument parentheses as well.

Call MySub(arg1, arg2)

Make of it what you wish, I think it's fairly pointless.

BTW in VB.NET both types of procedure call can be effected using the argument parentheses now, so in VB.NET the Call keyword truely is obsolete.

[Hack]

BTW in VB.NET both types of procedure call can be effected using the argument parentheses now, so in VB.NET the Call keyword truely is obsolete.

As it probably should have been in VB6.

[TheBionicOrange]

I'e noticed this in the past, and never really knew the difference between

Call MyProc(x,y)

as opposed to

MyProc x,y

I think some people like to use it as it "stands out" a bit more that the code is calling another routine.

[shirazamod]

What about if you want to call a process without passing it any arguments, would it be better to use Something() than to use Call Something?

[Hack]

What about if you want to call a process without passing it any arguments, would it be better to use Something() than to use Call Something?

It doesn't matter. Both of these will execute whatever code is in the Something Sub

Private Sub Command1_Click()
Something
End Sub
 
Private Sub Command1_Click()
Call Something
End Sub

[penagate]

Apart from the fact that you can't actually do Something(), only Something, like I said there's no difference.

In VB.NET, and other languages, it would be Something(), yes.