>________________________________ > From: Billy Stiltner <[email protected]> >To: Jonathan Wilkes <[email protected]> >Cc: "[email protected]" <[email protected]> >Sent: Wednesday, March 7, 2012 12:19 AM >Subject: Re: [PD] nonlocal message passing scope > > >I don't know if making it easier to do would be good for learning but it sure >would be easier for doing. haha!
Well, if you had abstraction wrappers for [s]/[r], [throw~]/[catch~], [s~]/[r~], [v], and dialog box entries for the "Put" menu array and iemguis (and possibly canvas properties), you wouldn't have to bother with $0 as a user. Plus a convenience abstraction to prefix a given symbol based on the scope you want, so that you can use it as a send-symbol inside message boxes. I guess the sticking points are objects that take an array name as an argument-- in the majority of cases those are settable, so I guess the user could choose between loadbanging a symbol or just using $0-prefixes there. There are probably other uses of $0 that I'm missing... [struct] names I guess, but there you're already punished for using $0 since it makes it impossible to reload scalar state. -Jonathan > >I try not to think about how that works. once I figured it out I wrote down >what I learned and use it as a reference or I'll just go look in a patch that >I have used in and duplicate. > > > _______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
