GetMemFragmentYou can use the
GetMemFragmentfunction to prepare a memory-based fragment.
OSErr GetMemFragment (Ptr memAddr, long length, Str63 fragName, LoadFlags findFlags, ConnectionID *connID, Ptr *mainAddr, Str255 errName);
- The address of the fragment.
- The size, in bytes, of the fragment.
- The name of the fragment. (This information is used primarily to allow you to identify the fragment during debugging.)
- A flag that specifies the operation to perform on the fragment. See the description of the
GetDiskFragmentfunction on page 3-19 for the values you can pass in this parameter.
- On exit, the connection ID that identifies the connection to the fragment. You can pass this ID to other Code Fragment Manager routines (for example,
- On exit, the main address of the fragment. The value returned is specific to the fragment itself.
- On exit, the name of the fragment that could not successfully be loaded. This parameter is meaningful only if the call to
GetMemFragmentfunction prepares for subsequent execution a fragment that
is already loaded into memory. This function is most useful for handling code that
is contained in a resource. You can read the resource data into memory using
normal Resource Manager routines (for example,
Get1Resource) and then call
GetMemFragmentto complete the processing required to prepare it for use (for example, to resolve any imports and execute the fragment's initialization routine).
- You must lock the resource-based fragment into memory (for example, by calling
HLock) before calling
GetMemFragment. You must not unlock the memory until you've closed the connection to the fragment (by calling
fragNoErr 0 No error paramErr -50 Parameter error fragLibNotFound -2804 Specified fragment not found fragHadUnresolveds -2807 Loaded fragment has unacceptable unresolved symbols fragNoMem -2809 Not enough memory for internal bookkeeping fragNoAddrSpace -2810 Not enough memory in user's address space for section fragObjectInitSeqErr -2812 Order error during user initialization function fragImportTooOld -2813 Import library is too old fragImportTooNew -2814 Import library is too new fragInitLoop -2815 Circularity in required initialization order
-2817 Error connecting to fragment fragUserInitProcErr -2821 Initialization procedure did not return
SEE ALSOSee "Loading Code Fragments" on page 3-10 for more details on the fragment-