Jeez, I'm sorry. I had actually seen that in the archives and decided to set readanysf~ aside for the time being. When I came back to it I forgot that I already knew what was causing the problem ;) That's a shame since a bunch of other externals (at least the versions I'm using) require flext 0.4.6.
Ummm... I wish I could debug it, but my knowledge of flext is nonexistant. Maybe something to do with the new build system? (which is very handy, btw).
Cheers, and sorry to disturb,
-Ian
august wrote:
Any thoughts? Oh, I'm running this on Debian SID w/ libmad 0.15.1b-1 and libvorbis 1.0.1-1
what version of FLEXT are you driving?
any version greater than 0.4.5 will crash PD hard. this has to due with the object wrapping in newer FLEXT versions.
Flext > 0.4.5 will wrap both "new" and "delete" calls in c++ to use pd's internal byte allocation/deallocation routines.
sorry about this. readanysf~ works fine with flext 0.4.5. Not sure why Thomas and other flext users are able to do "new" and "delete" calls in their code. I can't seem to nail down why that don't jive with my code.
-august.