Maybe you need to repost the problem. The [0][0] indecies don't even exist in the declaration of array?
Also you are trying to display an entire row of the array with the array[2] with a %d. Maybe that's something new in SV that I've never heard of before?
I suspect you are compiling the wrong file. "multiple array.bak" makes me think that this is a backup file and that you are editing "multiple array.sv" .
Otherwise, there doesn't seem to be anything other than the declaration of the array. Everything else is commented out leaving an empty initial block.
Nice. And the error is on the bracket as "bit" might be the name of a component or task defined in another file. One day we'll get clang-style error messages.
SystemVerilog **broken link removed**
Verilog **broken link removed**
Turns out there are quite a few deviations.
Anyone got any inclination into when we will get another Verilog/sv/vhdl standard released? It's about time they merged them into one super language/ have more commonality with keywords.
I read somewhere SV was supposed to be released as Verilog 2005 not as SV2005. The Acellera additions to the language got released with the wrong name. Now a lot of people think they are different languages, they aren't. All of Verilog exists in SV (or at least everything I use).
Maybe you'll see 10% support of new features by 2025, and then only the stuff you don't care about ;-)
They are slowly merging -- VHDL got the easy std_logic_vector to boolean conversion syntax. Verilog got structs (and more). It technically got functions on unconstrained vectors, but not in an obvious way.
However, people don't use existing synthesizable features. Vendors don't implement synthesis support for synthesizable features. And both languages are simulation-first with synthesis as a happy accident.
Add to this existing developers who actually like the old ways and there is little reason to add anything to the language that isn't for simulation.