Visual Basic, some keywords don't work

[deldan]

Hello,

I started VB scripting in EA 10. I have noticed that some VB keywords don't works e.g.:

Optional, as (in sub and function parameters types)

Code: [Select]

Function Works(package)
   Works = ""
End Function


Code: [Select]

Function Doesnt_Work_1(package as String)
   Doesnt_Work_1= ""
End Function


Code: [Select]

Function Doesnt_Work_2(Optional package = 100)
   Doesnt_Work_2= ""
End Function


Examples with prefix "Doesnt_Work" doesn't work in EA. I know they are correct because I have check them in Visual Studio.

It means that EA doesn't support fully VB or maybe I have to change some configuration?

[EXploringEA]

The scripting engine supports VBScript (plus JScript and JavaScript) which is not the same as Visual Basic - it's a different language that looks similar but has some different syntax, no typing, plus other limitations if you are used to VB but still useful.

Suggest you google a tutorial on VBScript to see examples and differences

Hope that helps explain why you are having issue.

[Geert Bellekens]

What make it difficult is that in EA you can write

Code: [Select]

dim myElement as EA.Elementand it will work. Even better, it allows you to use intellisense for attributes and operations.

When you try that in vanilla VBScript however you get an error.

Geert

[EXploringEA]

And it can be very frustrating making silly mistakes