Can't Dim walls

[Greogri]

Tried
Dim walls = {wall1, wall2, wall3, wall4}
But it says: Array initializers are valid only for arrays, but the type of 'wall' is 'Object'.

[dbasnett]

Uh.... walls is not dim'ed as an array.

See https://learn.microsoft.com/en-us/do...atures/arrays/

[Greogri]

So how can I do it?

[wes4dbt]

Uh.... walls is not dim'ed as an array.

See https://learn.microsoft.com/en-us/do...atures/arrays/

You know, that was my first thought. But this doesn't error and I have option strict On

        Dim wall1 As Object, wall2 As Object
        wall1 = "something"
        wall2 = 12345
        Dim walls = {wall1, wall2}

[Greogri]

There is 30 walls, I can't do that to 30 walls

[PlausiblyDamp]

Tried
Dim walls = {wall1, wall2, wall3, wall4}
But it says: Array initializers are valid only for arrays, but the type of 'wall' is 'Object'.

Is that the exact code giving the error and the exact error message? Seems strange the error message refers to "wall" but nowhere in the line of code you posted do you have anything declared as "wall".

How are wall1, wall2, etc declared?

[wes4dbt]

Is that the exact code giving the error and the exact error message? Seems strange the error message refers to "wall" but nowhere in the line of code you posted do you have anything declared as "wall".

How are wall1, wall2, etc declared?

Good catch

[Peter Porter]

How about just detectíng the color of the wall. If your sprite detects the color, it will not cross. Then you wont have to worry about creating so many objects.

[dbasnett]

So how can I do it?

Dim walls() ...

You were missing ()

[jmcilhinney]

The issue is that you have Option Strict Off and Option Infer Off. You should turn both On in the project properties and also in the VS options, so they are On by default in future projects.

With Option Infer On, the type of a variable can be inferred from the type of the initialising expression. You are initialising the walls variable with an array so it would be inferred to be that type. Because you have Option Infer Off, no type inference is performed.

With Option Strict On, you need to specify a type for everything. You can do so implicitly for an initialised variable with Option Infer On but, otherwise, you must do so explicitly. With Option Strict Off, any variable for which you don't specify a type will default to type Object.

You should ALWAYS have Option Strict On at the project level. It is Off by default primarily to make life easier for VB6 developers, particularly when upgrading existing code. Always turn it On and leave it On. In situations where you spe4cifically need late binding, turn it Off at the file level in only those files in which it is needed, using partial classes to keep the code in those files to an absolute minimum.

If you don't want to use type inference - some people find it confusing when variables are not explicitly typed - then you can turn Option Infer Off but then you should have to specify the type of the variable explicitly, because you should still have Option Strict On. If you have both On, your code will work fine as it is, because walls will be inferred to be the correct type. If you have Option Strict On and Option Infer Off then you need to specify the type explicitly:

Dim walls As SomeType() = {wall1, wall2, wall3, wall4}

where SomeType is the type of the array elements, whatever that is.

EDIT:

Actually, I just realised that this thread is tagged VS 2008. I'm not sure that Option Infer existed a decade and a half ago, when that was released. If it did then what I said above stands. If not, what I said above for having Option Infer Off is what you should follow. That and get yourself a more up-to-date version of VS unless you are required to use VS 2008 by work or school or the like. VS 2022 Community is free.