Stats

  • Locked Locked
  • Replies 7
  • Subscribers 64
  • Views 7706
  • 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

  • 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

  • Thanks Stephen
    agree that the ebst practice is to put them in a package. BTW it does not seems possible to define interfaces in a package as well (which is desirrable, IMO, sicne I'd put i a package everything that does not generate istances: right?)

    actually whe have just this version @Accent

    cheers


    Originally posted in cdnusers.org by marco.stanzani

  • 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

  • Posted By stephenh on 5/18/2007 6:42 AM

    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.

    Steve.
    Maybe it is worth adding that suggestion to the existing Error message as that would help the users in general a lot. How does one submit such "nice to have enhancement" if not via sourcelink? FWIW - I don't have sourcelink access as I'm not a NC customer but am running a verification services company in Bangalore.

    Regards
    Ajeetha, CVC
    www.noveldv.com


    Originally posted in cdnusers.org by ajeetha

  • Hi Ajeetha.

    I'll file that enhancement request - it makes sense.
    If you're using Cadence tools when working for your clients, I guess the best thing is to get your client to file the service request under their SourceLink account ID. There may be an alternative way that you can file them directly, but I'm not aware of it.

    Regards.
    Steve.


    Originally posted in cdnusers.org by stephenh

  • I filed enhance to improve error message. Thank you for the suggestion.

    Tim


    Originally posted in cdnusers.org by tpylant

  • Thanks Tim & Steve, glad to see the quick action to make the tool easy to use, appreciate it!

    Cheers
    Ajeetha, CVC
    www.noveldv.com


    Originally posted in cdnusers.org by ajeetha

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.