[PD] arguments not passed to an external

[Miller Puckette]

So probably best just to leave it unfixed.  I think lots of folks maintaining
librares wouldn't want someone else to come in and edit stuff for them.

cheers
M

On Mon, May 26, 2014 at 01:37:31PM -0700, Jonathan Wilkes wrote:
> Well the maintainer on a lot of it is Hans, and I doubt he wants to do it by hand.
> 
> -Jonathan
> 
> 
> 
> 
> On Monday, May 26, 2014 4:05 PM, Miller Puckette <msp at ucsd.edu> wrote:
>  
> 
> 
> I wouldn't dare unleash a script on SVN - I think it's wiser to leave this up
> to whomever is maintaining individual packages.
> 
> Same for whomever is watching over the howto (it's not my work at all, although
> I'm delighted it's there! )
> 
> M
> 
> 
> On Mon, May 26, 2014 at 12:22:15PM -0700, Jonathan Wilkes wrote:
> > Is there a script to change the rest of svn?
> > 
> > Also the externals howto should be changed to use A_CANT instead of zero.
> > 
> > -Jonathan
> > 
> > 
> > 
> > 
> > On Monday, May 26, 2014 3:00 PM, Miller Puckette <msp at ucsd.edu> wrote:
> >  
> > 
> > 
> > Aha... DOUBLE fail on my part - I wasn't enforcing A_CANT and anyhow
> > almost none fo teh tlde objects were using it!  Just goes to show -
> > if yuo've never tested something it probably doesn't work.
> > 
> > Should be fixed in vanilla git repo now.
> > 
> > cheers
> > M
> > 
> > 
> > On Mon, May 26, 2014 at 11:17:40AM -0700, Jonathan Wilkes wrote:
> > > I don't see anything in the code that would keep [dsp(--[osc~] from triggering this "dsp" message to the signal object.
> > > 
> > > Indeed, when I specify A_CANT as the "dsp" arg type for [osc~] and recompile it still crashes.
> > > 
> > > So that may be the policy, but the design doesn't keep the message from being dispatched.
> > > 
> > > -Jonathan
> > > 
> > > 
> > > On Monday, May 26, 2014 1:32 PM, Miller Puckette <msp at ucsd.edu> wrote:
> > >  
> > > 
> > > 
> > > No, the A_CANT will ensure that the message never gets sent to the
> > > object (because typechecking fails)
> > > 
> > > You can of course send the message from C, but anyone's allowed to crash
> > > Pd by introducing faulty C code :)
> > > 
> > > M
> > > 
> > > 
> > > On Mon, May 26, 2014 at 10:23:36AM -0700, Jonathan Wilkes wrote:
> > > > Is that by policy or design?
> > > > 
> > > > In other words, if I send a msd [dsp crash_my_pd( to a signal object that defines its dsp method args using A_CANT, will it still crash?  (Not at a machine with Pd or I'd try it myself.)
> > > > 
> > > > -Jonathan
> > > > 
> > > > 
> > > > On Monday, May 26, 2014 1:06 PM, Miller Puckette <msp at ucsd.edu> wrote:
> > > >  
> > > > 
> > > > 
> > > > Just to answer one sprcific question here...
> > > > > 
> > > > > Lyon's book explaing what A_GIMME does, but not A_CANT. I checked m_pd.h a
> > > > > bit but didn't make much out of it. It is there where the problem lies?
> > > > > 
> > > > 
> > > > A_CANT is used when an object receives a message but the arguments can't be
> > > > safely typechecked by Pd - so these messages are refued if sent by the patch,
> > > > but friendly C code can call them using a lower-level mechanism.
> > > > 
> > > > cheers
> > > > Miller
> 
> > _______________________________________________
> > Pd-list at lists.iem.at mailing list
> > UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list

> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list