Stats

  • Locked Locked
  • Replies 7
  • Subscribers 64
  • Views 7707
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

'class' not implemented??

archive

Hi there
I am compiling a class getting

ncvlog: *E,SVNIMP (/prj/so_asic/USERS/STANZANI/SO_ASIC/CONFIG/../DIGITAL/SIMULATION/TBENCH/so_i2s.v,52|17): SystemVerilog construct not yet implemented:  compilation unit top scope declaration.
class so_i2s_layer;

I am using version

ncvlog -ver
TOOL:   ncvlog  05.83-p002

how can it be claimed 'system verilog support' if classes (a key feature for SV) is not usable?

thanks


Originally posted in cdnusers.org by marco.stanzani
Parents

  • Hi Marco.

    At the moment, classes must be declared within a package, module or program.
    They're not permitted to "float" at the top level, hence the message you saw.

    I'd suggest you put any global classes into a package, and import that into whichever unit requires them.
    This makes for tidier encapsulation anyway :-)

    One last point, if you're using SystemVerilog, you'd do best to keep to the latest version, as that will have the best feature set. Currently the latest version is IUS6.1s2.

    Steve.


    Originally posted in cdnusers.org by stephenh
Reply

  • Hi Marco.

    At the moment, classes must be declared within a package, module or program.
    They're not permitted to "float" at the top level, hence the message you saw.

    I'd suggest you put any global classes into a package, and import that into whichever unit requires them.
    This makes for tidier encapsulation anyway :-)

    One last point, if you're using SystemVerilog, you'd do best to keep to the latest version, as that will have the best feature set. Currently the latest version is IUS6.1s2.

    Steve.


    Originally posted in cdnusers.org by stephenh
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.