> > If a 3rd party really needs to release a new .swc, then they can still > use the compc compiler as I think we are supposed to be getting that > too. By requiring them to use compc, we make it clear that they are > using old technology to do things the old way. > > Of course, having said all that, I may have missed the bleedin' obvious > elephant in the room as to why this won't work, so please do tell if > this is the case.
It sounds pretty plausible to me, although I'm not sure if it'll be practical not to support SWC's at all. There's a myriad of as3 libraries out there and quite probably a lot of folks that might only be interested in the SWF target. (At least for the foreseeable future). So then it might still be good practice to enable people to add SWC's to their build, but it that case only the SWF target will work. Until someone comes along and builds a preprocessor that can translate a SWC to a goshawk library :) cheers, Roland