Right thanks Nicolas, I'm all straight on that now and Flasc has been updated to reflect this ;)

I'm now double checking an issue with the tag selections for a project, but I think we're all good.

Thanks for taking the time Nicolas,

J

On 3/18/06, Nicolas Cannasse <[EMAIL PROTECTED]> wrote:
> Ok, so, CP's are what I've said they where, right?  A cp is just a path
> to where classes *might* be located that mtasc finds while compiling the
> classes.  it's not recursive though from what I experienced.

Just to explain it right, -cp is a base/root path for classes. Classes
are always looked up in subdirectories depending on their packages.

Let's say you have -cp c:\code and -cp ../mylib/somecode.

When MTASC will look for a class named my.pack.MyClass, it will search :

c:\code\my\pack\MyClass.as
../mylib/somecode/my/pack/MyClass.as

So basicaly even if you use a lot of packages, you only need one -cp as
long as all the classes are sharing one single root directory.

> If I have classes/com/blitzagency/Main.as and it
> references/uses com.blitzagency.controls.GraphicButton.as
> it won't find it unless I have classes/com/blitzagency/controls
> listed as a possible cp

All you need then is one single -cp classes
So you're kind of right when saying that -cp is not recursive, since
it's just a path appended to the left when looking for an AS file.

Nicolas

_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org



--
John Grden - Blitz
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to