[PD-dev] pow~ in Cyclone [was: Re: stripping down Pd-extended's default libs]

Hans-Christoph Steiner hans at eds.org
Wed Feb 18 18:02:18 CET 2009

On Feb 18, 2009, at 3:21 AM, IOhannes m zmoelnig wrote:

> Roman Haefeli wrote:
>> correct me, if this is wrong, but i understand, that overriding  
>> internal
>> classes doesn't work with single-file externals. so the feature of
>> overriding internal classes doesn't and won't work with pd-extended.
> not necessarily;
> i haven't checked, but imagine:
> 1.:
> [import cyclone]
> [pow~] will remain the vanilla version
> 2.:
> using [cyclone/pow~] will force the use of the single-object  
> external, and while doing so it will call the class_new() method for  
> "pow~" which will override the internal [pow~].
> [pow~] will become the cyclone version.
> this is both with (an imagined) Pd-extended 0.42

Would this be any different with a Pd-vanilla+libs 0.42?  I don't  
think there is anything particular to the Pd version in Pd-extended  
that would cause this, but instead the way the libraries are built.


>> please someone correct me, if this is wrong or based on wrong
>> assumptions.
> mfga.sdr
> IOhannes
> _______________________________________________
> Pd-dev mailing list
> Pd-dev at iem.at
> http://lists.puredata.info/listinfo/pd-dev


Terrorism is not an enemy.  It cannot be defeated.  It's a tactic.   
It's about as sensible to say we declare war on night attacks and  
expect we're going to win that war.  We're not going to win the war on  
terrorism.        - retired U.S. Army general, William Odom

More information about the Pd-dev mailing list