<html><head></head><body><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div><div dir="ltr">> Why is nobody complaining about not being able to use the third </div><div dir="ltr">> creation argument directly withing a message? What's the fuzz about the<br clear="none"><div class="ydp786548a0yqt7904893037" id="ydp786548a0yqtfd38988">> $0?</div></div><div dir="ltr"><br></div><div dir="ltr">$0 isn't part of the argument vector. It's a unique id automatically </div><div dir="ltr">generated for a patch/abstraction which the user happens to access </div><div dir="ltr">through a dollarsign variable.<br clear="none"></div><div dir="ltr"><br></div><div dir="ltr">That locality hack doesn't require that the unique id be fetched by </div><div dir="ltr">an unused dollarsign arg. For example, you could reserve the keyword </div><div dir="ltr">"let" such that a message box with "let token2" would get converted </div><div dir="ltr">behind the scenes to "1003-token2".</div><div dir="ltr"><br></div><div dir="ltr">When users for a decade have said they wanted $0 in msg boxes, </div><div dir="ltr">they mean that they want to use Pd's notion of send-symbol locality </div><div dir="ltr">inside message boxes. They want that instead of manually querying </div><div dir="ltr"> the value of a reserved dollarsign variable and sending that value </div><div dir="ltr">to the relevant message box in order to get "let" behavior.</div><div dir="ltr"><br></div><div dir="ltr">Also, since "$0" is already being used for this purpose it doesn't </div><div dir="ltr">make much sense to try to also get "$0" to refer to the selector. </div><div dir="ltr">You'd end up with inconsistent meaning where it fetches the </div><div dir="ltr">selector in msg boxes but not in object boxes. Plus you can </div><div dir="ltr">already get the selector of an incoming message with [list] </div><div dir="ltr">whereas you cannot get an abstraction's selector (which would </div><div dir="ltr">be handy for error reporting). So adding that inconsistency </div><div dir="ltr">would only duplicate existing functionality without adding </div><div dir="ltr">new functionality. </div><div dir="ltr"><br></div><div dir="ltr">-Jonathan<br></div><div dir="ltr"><br clear="none">> Roman</div><div id="ydp786548a0yahoo_quoted_3239162839" class="ydp786548a0yahoo_quoted"><div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;"><div><div class="ydp786548a0yqt7904893037" id="ydp786548a0yqtfd89569">_______________________________________________<br clear="none"><a shape="rect" href="mailto:Pd-list@lists.iem.at" rel="nofollow" target="_blank">Pd-list@lists.iem.at</a> mailing list<br clear="none">UNSUBSCRIBE and account-management -> <a shape="rect" href="https://lists.puredata.info/listinfo/pd-list" rel="nofollow" target="_blank">https://lists.puredata.info/listinfo/pd-list</a><br clear="none"></div></div>
</div>
</div></div></body></html>