# \#distributor

**URL:** https://verificationacademy.com/forums/tag/distributor/6836.md

[Latest](https://verificationacademy.com/forums/latest.md) · [Categories](https://verificationacademy.com/forums/categories.md) · [Tags](https://verificationacademy.com/forums/tags.md)

---

## [Distributing task calls between SV implementations in "generate" blocks](https://verificationacademy.com/forums/t/distributing-task-calls-between-sv-implementations-in-generate-blocks/35774)

<div class="topic-metadata">

**Author:** [@simonsabato](https://verificationacademy.com/forums/u/simonsabato)\
**Replies:** 4\
**Last updated:** [February 27, 2019, 7:47pm UTC](https://verificationacademy.com/forums/t/distributing-task-calls-between-sv-implementations-in-generate-blocks/35774 "2019-02-27T19:47:11Z")

</div>

In our “ram” library element, we compile in accessor tasks during simulation. Currently, we globally define LIB\_VENDOR or LIB\_BEHAVIORAL to control implementation. So we have code like: module ram; \`ifdef LIB\_VENDO…
