# Binding Issues Raised by Chris's PARSE-MACHINE

**URL:** <https://revolt.metaeducation.com/forum/t/binding-issues-raised-by-chriss-parse-machine/1937>\
**Category:** Binding\
**Created:** [January 26, 2021, 3:45am UTC](https://revolt.metaeducation.com/forum/t/binding-issues-raised-by-chriss-parse-machine/1937 "2021-01-26T03:45:09Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![rgchris](https://revolt.metaeducation.com/forum/user_avatar/revolt.metaeducation.com/rgchris/32/14_2.png) [@rgchris](https://revolt.metaeducation.com/forum/u/rgchris)\
**Post date:** [January 29, 2021, 5:08pm UTC](https://revolt.metaeducation.com/forum/t/binding-issues-raised-by-chriss-parse-machine/1937/4 "2021-01-29T17:08:58Z")

</div>

> [@hostilefork](#):
>
> In any case...my point stands, that you likely only intended here to **bind rules parser**. Yet with the historic workings of MAKE OBJECT!, when you do this with a COMPOSE and the block becomes a child of the object body, you will get the additional bindings of `name`, `suffixes`, `identify?`, `rules`, `options`, `decode`, `encode`... etc.

Ah, I get what you mean. Yep, that did catch me out. My inclination though is to reach for **map!** instead as it has no context and potentially doesn't require a preset list of fields, or another way of designating the rule (e.g. **[rule: bind 'rule 'some-other-word-in-the-parent-context-that-isnt-in-the-object]**—not ideal and a more nuanced constructor would be better in this instance). This goes back once again to thinking about what objects are for—1) single use, code-grouping objects such as this vs. 2) prototypes representing things in the classical object-oriented sense—which I'd still prefer to see prioritized. Again, I'm sympathetic to the need for different constructors, but still have reservations about the implications of **my/method** as a solution to binding when cloning. Anyways, this is more a response to [that topic](https://revolt.metaeducation.com/forum/t/breaking-make-object-into-component-operations/1442) than this one.

> [@hostilefork](#):
>
> Imagine adding `mark` to this list in your example...the user code bound to it could wind up corrupting state it wasn't supposed to see.

Specific usage of **mark** here is a behavioural legacy and a mistake, the convention I'm looking to use here would be **state/mark**. I'm not sure I see the **state** basket as being heavy handed, I think it's a reasonable response to the complexity of what I'm trying to achieve. Could well also be my familiarity bias too, but for now it's workable as a means to explore the Parse Machine concept to a conclusion.

---

_[View the full topic](https://revolt.metaeducation.com/forum/t/binding-issues-raised-by-chriss-parse-machine/1937)._
