Geoffrey Coram

You need these two to free allocated vector and string parameters when an instance gets destroyed. Why doesn't OSDI free those vectors when it destroys the instance?

It looks like 0.4 adds two functions, but I'm wondering why they are needed. I have a test that uses $param_given in the Verilog-A module, and it works fine with OSDI 0.3. // 0.3 ends here uint32_t (*given_flag_model)(void *model, uint32_t id); uint32_t (*given_flag_instance)(void *inst, uint32_t id);

osdi/osdiinit.c: errMsg = tprintf("Unkown OSDI type %d for parameter %s!",

Also "initalization" should be "initialization" osdi/osdisetup.c: errMsg = tprintf("%i errors occurred during initalization", info.num_errors);

typo in error message (and internal variables)

Does LGPL actually require that these files be modifiable? These header files are...

And actually, there's no particular reason that ADMS needs to include the header...

The mail thread there sort of misses the point; the VAMS header files are copyrighted,...