The representation of a SWC. Contains the main entry points for the compiler to use when getting information about a SWC. A Swc can be used by multiple threads at the same time so it should not hold onto anything from a specific compile. It also can be dumped when its stale so it should not be stored (or pieces of it stored, like the Catalog) from anywhere other than SwcGroup. Reading: - A SWC can exist in a partially decoded state. - When the SWC is fully read, it is FULLY READ AND CLOSED, and the backing file can be deleted. - The SWC should be able to discern if the in-memory snapshot is out of date. Writing: - The state of the SWC object after writing should be the same as if it had been fully read in. Updating: - The SWC should be entirely rewritten to a temporary location, then copied atomically to the new location.
@author Brian Deitte
@author Roger Gonzalez
All source code are property of their respective owners. Java is a trademark of Sun Microsystems, Inc and owned by ORACLE Inc. Contact coftware#gmail.com.