ddDeleteObj() and its warnings

I can't really see why ddDeleteObj should be causing sch or db warnings, unless there's some triggers in place (maybe as part of a design management integration?) to do some checks? I'm guessing here - but there's certainly no specific way with ddDeleteObj to deal with these warnings.

In current versions you have the muffleWarnings() construct that you could surround your code with to swallow any warnings. muffleWarnings was introduced in IC618/ICADVM181 ISR1.

Andrew.

Thank you Andrew.

Unfortunately, I am using IC616 and so I cannot use muffleWarnings(). I tried also to disable the design management sw, but I continue having warnings.

Best regards,

Aldo

Hi Aldo you could use the CCFcaptureWarnings macro or this code if you don't care about capturing the warnings in a variable:

/* abMuteWarnings.il

Author     A.D.Beckett
Group      Custom IC (UK), Cadence Design Systems Ltd.
Language   SKILL
Date       Dec 31, 2018 
Modified   
By         

A macro to mute the output from anything sent to woport (warnings).
Based on abMute (written many years ago)

abMuteWarnings(warn("test this\n") warn(""))

will produce nothing.

Relies on SKILL's dynamic scoping, so will not work in SKILL++
unless you do:

inSkill(abMuteWarnings(warn("test this\n") warn("")))

***************************************************

SCCS Info: @(#) abMuteWarnings.il 12/31/18.11:36:17 1.1

*/

(defmacro abMuteWarnings (@rest body)
  `(progn
     (unless (openportp (getqq abMuteWarnings nullport))
       (putpropqq abMuteWarnings (outfile "/dev/null") nullport))
     (let ((woport (getqq abMuteWarnings nullport)))
       ,@body
       )
     )
  )

You can then just use:

foreach(cellId ddGetObj(libName)~>cells
    abMuteWarnings(ddDeleteObj(cellId))
)

Regards,

Andrew

Thank you, Andrew. It works.

Just a clarification: Lint sees woport variable as unused. Is it possible to have "clean" Lint report?

Thank you

Best regards,

Aldo

I don't see woport reported just by using these macros, but I can see the you might get it if you have something like this:

let(((nullport outfile("/dev/null")))
  let(((woport nullport))
    warn("this")
    warn("that")
    getWarn()
  )
)

I think the only way to suppress the message is to do:

skIgnoreMessage("Unused")

but that will suppress all unused variables. I don't believe there's a more selective way of ignoring specific variables. Of course, you could cheat by doing:

let(((nullport outfile("/dev/null")))
  let(((woport nullport))
    ; reference to a variable just to get clean Lint score
    woport
    warn("this")
    warn("that")
    getWarn()
  )
)

Personally I don't like doing that - I'd sooner just document the reasons for a score being lower.

Andrew