Nope. Externals are compiled, the source-code that went into them is
gone.

If you want to see the open source equivalents of some of the Max
externals, check out PD. Not all of the objects are there, doesn’t
have even close to the amount of polish in Max.

You’re better off redesigning your c/c++ project anyhow and just
using the main ideas of your Max patch.

_Mark

yeah mine.
Also, i know that yann orlaray (sorry if the spelling is wrong) in lyon
made a wrapper that converts your max patches
into C code…
I’ve never seen it but i’ve heard a lot about it.

Also, loads of third party externals are often donwloadable with their
source code (which is normal to me… but
that’s an other subject…)
I don’t think this is what you’re looking for but at least… it makes you
read c code for max-msp-jitter and it’s always
interesting, isn’t it ?

On 15-Jun-2006, at 1:16, Mark Pauley wrote:
> Nope. Externals are compiled, the source-code that went into them
> is gone.

Not entirely: the SDK publishes source for about two dozen objects,
and numerous 3rd party objects come with source attached.

Justin: you should take a look at the Max SDK. Then you will better
understand why manual conversion from prototype to C/C++/whatever is
the only realistic path. Understanding the underlying architecture
will also help you tread that path.

Good luck, P.

————– http://www.bek.no/~pcastine/Litter/ ————-
Peter Castine +–> Litter Power & Litter Bundle for Jitter

iCE: Sequencing, Recording & |home | chez nous|
Interface Building for |bei uns | i nostri|
Max/MSP Extremely cool http://www.castine.de
http://www.dspaudio.com/

The forum only just exists for a few months, before this was a mailinglist..