# FYI - using prolog\_frame\_attribute/3 and parent

**URL:** <https://swi-prolog.discourse.group/t/fyi-using-prolog-frame-attribute-3-and-parent/4596>\
**Category:** Help!\
**Created:** [October 26, 2021, 11:56am UTC](https://swi-prolog.discourse.group/t/fyi-using-prolog-frame-attribute-3-and-parent/4596 "2021-10-26T11:56:09Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jan](https://yyz2.discourse-cdn.com/free1/user_avatar/swi-prolog.discourse.group/jan/32/4_2.png) [@jan](https://swi-prolog.discourse.group/u/jan)\
**Post date:** [October 26, 2021, 12:32pm UTC](https://swi-prolog.discourse.group/t/fyi-using-prolog-frame-attribute-3-and-parent/4596/2 "2021-10-26T12:32:51Z")

</div>

I don’t know the details of your code. A quick read hints that you are using a frame reference (much) later. You are responsible that it is still valid. The reference is just an integer that goes through some very elementary checks. Surely not something fool proof. A fool proof solution would generate unique ids and keep track of those. That is a lot of complicated admin. Typically you get a frame reference from the trace interception and a few more predicates, do you analysis and forget about it. If you want to do anything different you have to be very careful about the scoping rules.

These predicates are for a reason in the _Hacker’s corner_ 🙂

---

_[View the full topic](https://swi-prolog.discourse.group/t/fyi-using-prolog-frame-attribute-3-and-parent/4596)._