# Generic Quoting Makes Headway on MAKE OBJECT!

**URL:** <https://revolt.metaeducation.com/forum/t/generic-quoting-makes-headway-on-make-object/997>\
**Category:** Internals\
**Created:** [January 5, 2019, 8:39am UTC](https://revolt.metaeducation.com/forum/t/generic-quoting-makes-headway-on-make-object/997 "2019-01-05T08:39:43Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![hostilefork](https://revolt.metaeducation.com/forum/user_avatar/revolt.metaeducation.com/hostilefork/32/421_2.png) [@hostilefork](https://revolt.metaeducation.com/forum/u/hostilefork)\
**Post date:** [January 20, 2024, 7:24am UTC](https://revolt.metaeducation.com/forum/t/generic-quoting-makes-headway-on-make-object/997/4 "2024-01-20T07:24:42Z")

</div>

> [@hostilefork](#):
>
> Here we see these loopholes getting closed. The make is actually able to produce a structurally identical object _(like I said, let's avoid talking about binding, that's its own conversation)_.

Speaking a _little_ about binding...

...given how [pure virtual binding](https://revolt.metaeducation.com/forum/t/rebol-and-scopes-well-why-not/1751) is evolving, we are now considering BLOCK! to be "evaluative" because it will pick up bindings from the local environment... while quoted things will not. _(The previous iteration of pure virtual binding had all values--including quoted ones--getting binding, because binding propagation was done in all structural operations... including PICK and FOR-EACH... leading to a mire of multiply-applied binding that is now being reined in with the consequence of living in a mostly-unbound world.)_

To be consistent here, we'll need anywhere a BLOCK is being represented "by value under evaluation" to quote it:

```
 >> block: '[foo]

 >> foo: <bar>

 >> obj: make object! [b: block]
 == make object! [
     b: '[foo]
 ]

```

Use your imagination that we're actually in a rich terminal where that block "argument" to the MAKE OBJECT! is a rendering of something that you could get the address of and execute. If you did, you would want that quote on the [foo] block to indicate that it should not pick up a binding.

Thanks to doing string interpolation [by putting strings in blocks](https://revolt.metaeducation.com/forum/t/could-strings-have-context/587/27) vs. giving strings bindings, this won't be needed for strings.

---

_[View the full topic](https://revolt.metaeducation.com/forum/t/generic-quoting-makes-headway-on-make-object/997)._
