This change should not affect any current usage, but adds possibility to define the actor for the axi_slave being created. For some reason on a test needing several AXI Slave VCIs, modelsim put all of them under the same "id" and things got awkward.

This has solved it.

There is work being done to standardize some parts of VCs and VCIs to improve interoperability. One of the rules of that standard is to have the ability you're looking for. All present VCs have been modified to comply with this standard but that work hasn't been merged yet. It's been on hold for a while but is number two on my prio list and I will get to it shortly.

We can do this before that as it doesn't break any backward compatibility but please have a look at

I made the changes, but It is still having trouble on some seemingly unrelated checks.

@rftafas the linter errors are unrelated to your changes. However, I think that acceptance and vcomponents failures are related to this PR. Precisely, the AXI DMA example is failing in acceptance tests, and AXI Slave tests are failing in vcomponents.

It seems that the change from 'new_actor' to 'null_actor' caused this. Most probably, the examples will have to be adapted to include an actor now, as it does not do that anymore.