On Thu, 19 Jan 2006, Hans-Christoph Steiner wrote:
Sounds good, this is how I structured PDa, so it would reduce the differences between PDa and standard pd.
Do you have any documentation on this? It would be good to have Pd and PDa as similar as possible. Plus its always good to have an example to start from.
You can download PDa and look at the source. But it is so trivial to change the behaviour (in some cases), that it is not even necessary.
Just delete the xxx_setup() function from the pd source and move all the xxx_* code into a separate file and treat it as an external.
But then, there are some things which make this a bit more complicated in some cases. e.g. as Thomas noted if you want to reuse code in several "internals/externals". This might be important in the SIMD case, but maybe you can factor out standard operations into macros and reuse those. For PDa I had to come up with a workaround for sine tables that are used by some oscillators.
And, I just made the signal processing objects external up to now, so I don't know what problems will arise with others ...
Guenter
.hc
Günter
.hc
__ ____
"The arc of history bends towards justice." - Dr. Martin Luther King,Jr.
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
http://at.or.at/hans/
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev