# RFC for Table of Constants TZIP

**URL:** https://forum.tezosagora.org/t/rfc-for-table-of-constants-tzip/2579
**Category:** TZIP
**Created:** [January 5, 2021, 3:43am UTC](https://forum.tezosagora.org/t/rfc-for-table-of-constants-tzip/2579 "2021-01-05T03:43:17Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![rafoo](https://forum.tezosagora.org/letter_avatar_proxy/v4/letter/r/f08c70/32.png) [@rafoo](https://forum.tezosagora.org/u/rafoo)
#### Post date: [January 26, 2021, 10:09pm UTC](https://forum.tezosagora.org/t/rfc-for-table-of-constants-tzip/2579/5 "2021-01-26T22:09:44Z")

</div>

Isn’t this proposal less generic than the one about views ([Views TZIP](https://forum.tezosagora.org/t/views-tzip/2560))? Assuming we have views I can register a constant `c` named `n` of type `ty` by originating the contract `parameter never; storage unit; code {CAR; NEVER}; view n unit ty {DROP; PUSH ty c}` and then I can access it by calling `PUSH address "KT1.."; UNIT; VIEW n unit ty` or am I missing something?

---

_[View the full topic](https://forum.tezosagora.org/t/rfc-for-table-of-constants-tzip/2579)._