• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. 'class' not implemented??

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
archive over 18 years ago

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
  • Cancel
Parents
  • archive
    archive over 18 years ago

    FWIW: Interfaces are more like a module. They are instanced, etc and many tools even search for them like modules if you use the -y directive. So I would not think putting them in a package would be a good thing.


    Originally posted in cdnusers.org by bryan
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 18 years ago

    FWIW: Interfaces are more like a module. They are instanced, etc and many tools even search for them like modules if you use the -y directive. So I would not think putting them in a package would be a good thing.


    Originally posted in cdnusers.org by bryan
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information