How to delete all outputs for test in ADE-XL/Assembler using SKILL

Hi Alex,

The maeDeleteOutput and axlDeleteOutput functions do work - you just have to pass them the signal or the expression if they are unnamed. It's possible the code below is incomplete and doesn't handle all output types though:

foreach(testOutput testOutputList
  cond(
    (testOutput->name axlDeleteOutput(session test_name testOutput->name))
    (testOutput->signal axlDeleteOutput(session test_name testOutput->signal))
    (testOutput->expression axlDeleteOutput(session test_name sprintf(nil "%L" testOutput->expression)))
  )
)

I think there's an argument to provide a function which retrieves the "name" for each output - i.e. the name that can be passed to axlDeleteOutput/maeDeleteOutput. Perhaps an maeGetOutputNames() or something like that? Worth contacting customer support to ask for such a function - because the above requires a bit too much knowledge of the way things are stored.

Andrew.

Alex,

Don't have time to test this today, but you might be able to suppress the warning by calling getWarn() after each axlDeleteOutput. However, if the warning is already flushed by the code then that won't work.

The other way to suppress the warnings is to surround the code that does the deletion with something like this:

let(((nullport (outfile "/dev/null")))
  let(((woport nullport))
    ; do the loop with all the deletion here
  )
  close(nullport)
)

This is using SKILL's dynamic scoping to temporarily reassign woport to write to /dev/null. The benefit of using this scoping-based way of doing it is that if the code aborts with an error for some reason, the stack unwinding will cause woport to be restored to its standard value.

If you have a concern about performance, it may make sense to contact customer support to request a function to delete all the outputs; I suspect doing it one at a time is doing a bunch of synchronisation per delete, and it may be more efficient to be able to delete them all in one go. Unfortunately the functions that I can think of to do that are private - so this would probably need an enhancement CCR to improve.

Regards,

Andrew.

You're quite right - it is. That's a bit strange (I can see where in the code this happens). Anyway, the higher level function which can delete multiple outputs also provides the option to suppress these warnings, but the API to do it isn't public (and I'm not sure it's complete in itself and not so friendly for maestro or adexl views).

Regards,

Andrew.