John Grden wrote: > then why have packs then? i thought a CP was just the same idea as a pack.
A codepath is just that: A path in which mtasc should look for code. The way this works is that mtasc parses the classes you supply as arguments and includes all other classes referenced by these recursively. If it doesn't find one of these classes in the current directory, it starts looking in each of the directories supplied by using the -cp argument. The -pack argument on the other side instructs mtasc to (non-recursively) pack all the classes in the given directory into the swf. AFAIK, it's primarily meant for people that use lots of linked symbols with classes registered to them that aren't referenced anywhere else and don't get compiled by mtasc if they aren't specifically included, be it by supplying the as individual arguments or by using -pack. I think the reason for not making -pack recurse is to prevent the inclusion of unneeded classes. (Though I'm not so sure of whether that's a good decision ...) cheers, till _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
