<h1>xercesc::XMLPlatformUtils Class Reference</h1><!-- doxytag: class="xercesc::XMLPlatformUtils" -->Utilities that must be implemented in a platform-specific way.
<tr><tdclass="mdescLeft"> </td><tdclass="mdescRight">Aligns the specified pointer per platform block allocation requirements. <ahref="#3cd3016fbc19c052f4d0e070e8b53027"></a><br></td></tr>
<tr><tdclass="mdescLeft"> </td><tdclass="mdescRight">Opens the standard input as a file. <ahref="#9931e001ce1ec647e629da1bb6ec8748"></a><br></td></tr>
<tr><tdclass="mdescLeft"> </td><tdclass="mdescRight">Gets the full path from a relative path. <ahref="#dee1b55606f98d42446b75ba3330d578"></a><br></td></tr>
<tr><tdclass="mdescLeft"> </td><tdclass="mdescRight">Gets the current working directory. <ahref="#0a3cf7e45d7779ff70abd9cd04aca38a"></a><br></td></tr>
<tr><tdclass="mdescLeft"> </td><tdclass="mdescRight">Check if a charater is a slash. <ahref="#5d11cab9d17eace29c57adaf9fffc993"></a><br></td></tr>
<tr><tdclass="mdescLeft"> </td><tdclass="mdescRight">Remove occurences of the pair of dot slash. <ahref="#d331e46bd8e98c658607b7c5ee5309bb"></a><br></td></tr>
<tr><tdclass="mdescLeft"> </td><tdclass="mdescRight">Remove occurences of the dot dot slash. <ahref="#82adca6243984fa993c76b7111ac3cc2"></a><br></td></tr>
<tr><tdclass="mdescLeft"> </td><tdclass="mdescRight">Determines if a path is relative or absolute. <ahref="#f299e7bdd861ad61670fdc024e5497a7"></a><br></td></tr>
<tr><tdclass="mdescLeft"> </td><tdclass="mdescRight">Gets the system time in milliseconds. <ahref="#7a44e8540b03f08370471ff6fd0628b9"></a><br></td></tr>
<tr><tdclass="mdescLeft"> </td><tdclass="mdescRight">Loads the message set from among the available domains. <ahref="#e9764323981fa35b0565ae12e9158f4e"></a><br></td></tr>
<tr><tdclass="mdescLeft"> </td><tdclass="mdescRight">Conditionally updates or returns a single word variable atomically. <ahref="#4973516510fc560ec9410803f9a685f0"></a><br></td></tr>
<tr><tdcolspan="2"><divclass="groupHeader">Atomic Increment and Decrement</div></td></tr>
<tr><tdclass="mdescLeft"> </td><tdclass="mdescRight">Increments a single word variable atomically. <ahref="#4534bc666d6adfc99c416bf559b2ab63"></a><br></td></tr>
<tr><tdclass="mdescLeft"> </td><tdclass="mdescRight">Decrements a single word variable atomically. <ahref="#b102479964d69682de97c318237e50b7"></a><br></td></tr>
<tr><tdcolspan="2"><divclass="groupHeader">NEL Character Handling</div></td></tr>
<tr><tdclass="mdescLeft"> </td><tdclass="mdescRight">This function enables the recognition of NEL(0x85) char and LSEP (0x2028) as newline chars which is disabled by default. <ahref="#2ca31a9fec4bdc937eef20d8f368af41"></a><br></td></tr>
<tr><tdclass="mdescLeft"> </td><tdclass="mdescRight">Return the value of fgNEL flag. <ahref="#26eb661a28e85d71071513267d745e6f"></a><br></td></tr>
<tr><tdclass="mdescLeft"> </td><tdclass="mdescRight">Returns whether a strict IANA encoding name check is enabled or disabled. <ahref="#3acffa5db6af9518011b00e5a7530dce"></a><br></td></tr>
<tr><tdcolspan="2"><br><h2>Static Public Attributes</h2></td></tr>
Utilities that must be implemented in a platform-specific way.
<p>
This class contains methods that must be implemented in a platform specific manner. The actual implementations of these methods are available in the per-platform files indide <code>src/util/Platforms </code>.
This must be implemented by the per-platform driver. The atomicDecrement subroutine increments one word in a single atomic operation. This operation is useful when a counter variable is shared between several threads or processes. When updating such a counter variable, it is important to make sure that the fetch, update, and store operations occur atomically (are not interruptible).<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>location</em> </td><td>Specifies the address of the word variable to be decremented.</td></tr>
</table>
</dl>
<dlcompact><dt><b>Returns:</b></dt><dd>The function return value is positive if the result of the operation was positive. Zero if the result of the operation was zero. Negative if the result of the operation was negative. Except for the zero case, the value returned may differ from the actual result of the operation - only the sign and zero/nonzero state is guaranteed to be correct. </dd></dl>
This must be implemented by the per-platform driver. The atomicIncrement subroutine increments one word in a single atomic operation. This operation is useful when a counter variable is shared between several threads or processes. When updating such a counter variable, it is important to make sure that the fetch, update, and store operations occur atomically (are not interruptible).<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>location</em> </td><td>Specifies the address of the word variable to be incremented.</td></tr>
</table>
</dl>
<dlcompact><dt><b>Returns:</b></dt><dd>The function return value is positive if the result of the operation was positive. Zero if the result of the operation was zero. Negative if the result of the operation was negative. Except for the zero case, the value returned may differ from the actual result of the operation - only the sign and zero/nonzero state is guaranteed to be correct. </dd></dl>
This must be implemented by the per-platform driver, which should use local file services to close the passed file handle, and to destroy the passed file handle and any allocated data or system resources it contains.<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>theFile</em> </td><td>The file handle to close </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>manager</em> </td><td>The <aclass="el"href="classxercesc_1_1MemoryManager.html">MemoryManager</a> to use to allocate objects </td></tr>
Conditionally updates or returns a single word variable atomically.
<p>
This must be implemented by the per-platform driver. The compareAndSwap subroutine performs an atomic operation which compares the contents of a single word variable with a stored old value. If the values are equal, a new value is stored in the single word variable and TRUE is returned; otherwise, the old value is set to the current value of the single word variable and FALSE is returned.<p>
The compareAndSwap subroutine is useful when a word value must be updated only if it has not been changed since it was last read.<p>
Note: The word containing the single word variable must be aligned on a full word boundary.<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>toFill</em> </td><td>Specifies the address of the single word variable </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>newValue</em> </td><td>Specifies the new value to be conditionally assigned to the single word variable. </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>toCompare</em> </td><td>Specifies the address of the old value to be checked against (and conditionally updated with) the value of the single word variable.</td></tr>
</table>
</dl>
<dlcompact><dt><b>Returns:</b></dt><dd>Returns the new value assigned to the single word variable </dd></dl>
This must be implemented by the per-platform driver, which should use local file services to deterine the current position within the passed file.<p>
Since the file API provided here only reads, if the host platform supports separate read/write positions, only the read position is of any interest, and hence should be the one returned.<p>
<tr><tdvalign="top"></td><tdvalign="top"><em>manager</em> </td><td>The <aclass="el"href="classxercesc_1_1MemoryManager.html">MemoryManager</a> to use to allocate objects </td></tr>
This must be implemented by the per-platform driver, which should use local file services to determine the current size of the file represented by the passed handle.<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>theFile</em> </td><td>The file handle whose size you want </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>manager</em> </td><td>The <aclass="el"href="classxercesc_1_1MemoryManager.html">MemoryManager</a> to use to allocate objects </td></tr>
</table>
</dl>
<dlcompact><dt><b>Returns:</b></dt><dd>Returns the size of the file in bytes </dd></dl>
This must be implemented by the per-platform driver. It returns the current working directory is. <dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>manager</em> </td><td>The <aclass="el"href="classxercesc_1_1MemoryManager.html">MemoryManager</a> to use to allocate objects </td></tr>
</table>
</dl>
<dlcompact><dt><b>Returns:</b></dt><dd>Returns the current working directory. This is dyanmically allocated and must be deleted by the caller when its no longer needed! The memory returned will be allocated using the static memory manager, if users do not supply a memory manager. Users then need to make sure to use either the default or user specific memory manager to deallocate the memory. </dd></dl>
<tdclass="md"nowrapvalign="top">static unsigned long xercesc::XMLPlatformUtils::getCurrentMillis </td>
<tdclass="md"valign="top">( </td>
<tdclass="mdname1"valign="top"nowrap></td>
<tdclass="md"valign="top"> ) </td>
<tdclass="md"nowrap><code> [static]</code></td>
</tr>
</table>
</td>
</tr>
</table>
<tablecellspacing="5"cellpadding="0"border="0">
<tr>
<td>
</td>
<td>
<p>
Gets the system time in milliseconds.
<p>
This must be implemented by the per-platform driver, which should use local services to return the current value of a running millisecond timer. Note that the value returned is only as accurate as the millisecond time of the underyling host system.<p>
<dlcompact><dt><b>Returns:</b></dt><dd>Returns the system time as an unsigned long </dd></dl>
This must be implemented by the per-platform driver. It should complete a relative path using the 'current directory', or whatever the local equivalent of a current directory is. If the passed source path is actually fully qualified, then a straight copy of it will be returned.<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>srcPath</em> </td><td>The path of the file for which you want the full path</td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>manager</em> </td><td>Pointer to the memory manager to be used to allocate objects.</td></tr>
</table>
</dl>
<dlcompact><dt><b>Returns:</b></dt><dd>Returns the fully qualified path of the file name including the file name. This is dyanmically allocated and must be deleted by the caller when its no longer needed! The memory returned will beallocated using the static memory manager, if user do not supply a memory manager. Users then need to make sure to use either the default or user specific memory manager to deallocate the memory. </dd></dl>
Initialization <b>must</b> be called first in any client code.<p>
The locale is set iff the <aclass="el"href="classxercesc_1_1XMLPlatformUtils.html#f72fdf4110e3458cbf5f7f6b108f8d06">Initialize()</a> is invoked for the very first time, to ensure that each and every message loaders, in the process space, share the same locale.<p>
All subsequent invocations of <aclass="el"href="classxercesc_1_1XMLPlatformUtils.html#f72fdf4110e3458cbf5f7f6b108f8d06">Initialize()</a>, with a different locale, have no effect on the message loaders, either instantiated, or to be instantiated.<p>
To set to a different locale, client application needs to <aclass="el"href="classxercesc_1_1XMLPlatformUtils.html#865c8490106f9a6323486c7b80a3fba1">Terminate()</a> (or multiple <aclass="el"href="classxercesc_1_1XMLPlatformUtils.html#865c8490106f9a6323486c7b80a3fba1">Terminate()</a> in the case where multiple <aclass="el"href="classxercesc_1_1XMLPlatformUtils.html#f72fdf4110e3458cbf5f7f6b108f8d06">Initialize()</a> have been invoked before), followed by Initialize(new_locale).<p>
The default locale is "en_US".<p>
nlsHome: user specified location where MsgLoader retrieves error message files. the discussion above with regard to locale, applies to this nlsHome as well.<p>
panicHandler: application's panic handler, application owns this handler. Application shall make sure that the plugged panic handler persists through the call to XMLPlatformUtils::terminate().<p>
memoryManager: plugged-in memory manager which is owned by user applications. Applications must make sure that the plugged-in memory manager persist through the call to XMLPlatformUtils::terminate() </td>
This must be implemented by the per-platform driver, which should determine whether the passed path is relative or not. The concept of relative and absolute might be... well relative on different platforms. But, as long as the determination is made consistently and in coordination with the <aclass="el"href="classxercesc_1_1XMLPlatformUtils.html#77a8cf5c5e50e631ee96249da8ea3a49">weavePaths()</a> method, it should work for any platform.<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>toCheck</em> </td><td>The file name which you want to check </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>manager</em> </td><td>The <aclass="el"href="classxercesc_1_1MemoryManager.html">MemoryManager</a> to use to allocate objects </td></tr>
</table>
</dl>
<dlcompact><dt><b>Returns:</b></dt><dd>Returns true if the filename appears to be relative </dd></dl>
Each per-platform driver must implement this. Only it knows what the actual content of the passed mutex handle is. The returned handle pointer will be eventually passed to <aclass="el"href="classxercesc_1_1XMLPlatformUtils.html#dcbe4c8486c8051fb13bcd6fe695b99d">closeMutex()</a> which is also implemented by the platform driver.<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>manager</em> </td><td>The <aclass="el"href="classxercesc_1_1MemoryManager.html">MemoryManager</a> to use to allocate objects </td></tr>
This must be implemented by the per-platform driver, which should use local file services to open the passed file. If it fails, a null handle pointer should be returned.<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>fileName</em> </td><td>The string containing the name of the file </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>manager</em> </td><td>The <aclass="el"href="classxercesc_1_1MemoryManager.html">MemoryManager</a> to use to allocate objects </td></tr>
</table>
</dl>
<dlcompact><dt><b>Returns:</b></dt><dd>The file handle of the opened file </dd></dl>
This must be implemented by the per-platform driver, which should use local file services to open passed file. If it fails, a null handle pointer should be returned.<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>fileName</em> </td><td>The string containing the name of the file </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>manager</em> </td><td>The <aclass="el"href="classxercesc_1_1MemoryManager.html">MemoryManager</a> to use to allocate objects </td></tr>
</table>
</dl>
<dlcompact><dt><b>Returns:</b></dt><dd>The file handle of the opened file </dd></dl>
This must be implemented by the per-platform driver, which should use local file services to open the passed file. If it fails, a null handle pointer should be returned.<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>fileName</em> </td><td>The string containing the name of the file </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>manager</em> </td><td>The <aclass="el"href="classxercesc_1_1MemoryManager.html">MemoryManager</a> to use to allocate objects </td></tr>
</table>
</dl>
<dlcompact><dt><b>Returns:</b></dt><dd>The file handle of the opened file </dd></dl>
This must be implemented by the per-platform driver, which should use local file services to open passed file. If it fails, a null handle pointer should be returned.<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>fileName</em> </td><td>The string containing the name of the file </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>manager</em> </td><td>The <aclass="el"href="classxercesc_1_1MemoryManager.html">MemoryManager</a> to use to allocate objects </td></tr>
</table>
</dl>
<dlcompact><dt><b>Returns:</b></dt><dd>The file handle of the opened file </dd></dl>
This must be implemented by the per-platform driver, which should use local file services to open a handle to the standard input. It should be a copy of the standard input handle, since it will be closed later!<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>manager</em> </td><td>The <aclass="el"href="classxercesc_1_1MemoryManager.html">MemoryManager</a> to use to allocate objects </td></tr>
</table>
</dl>
<dlcompact><dt><b>Returns:</b></dt><dd>The file handle of the standard input stream </dd></dl>
If, during initialization, we cannot even get far enough along to get transcoding up or get message loading working, we call this method.<p>
Each platform can implement it however they want. This method will delegate the panic handling to a user specified panic handler or in the absence of it, the default panic handler.<p>
In case the default panic handler does not support a particular platform, the platform specific panic hanlding shall be implemented here .<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>reason</em> </td><td>The enumeration that defines the cause of the failure </td></tr>
This must be implemented by the per-platform driver, which should use local file services to read up to 'toRead' bytes of data from the passed file, and return those bytes in the 'toFill' buffer. It is not an error not to read the requested number of bytes. When the end of file is reached, zero should be returned.<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>theFile</em> </td><td>The file handle to be read from. </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>toRead</em> </td><td>The maximum number of byte to read from the current position </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>toFill</em> </td><td>The byte buffer to fill </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>manager</em> </td><td>The <aclass="el"href="classxercesc_1_1MemoryManager.html">MemoryManager</a> to use to allocate objects</td></tr>
</table>
</dl>
<dlcompact><dt><b>Returns:</b></dt><dd>Returns the number of bytes read from the stream or file </dd></dl>
This function enables the recognition of NEL(0x85) char and LSEP (0x2028) as newline chars which is disabled by default.
<p>
It is only called once per process. Once it is set, any subsequent calls will result in exception being thrown.<p>
Note: 1. Turning this option on will make the parser non compliant to XML 1.0. 2. This option has no effect to document conforming to XML 1.1 compliant, which always recognize these two chars (0x85 and 0x2028) as newline characters. </td>
To remove the sequence, slash dot dot slash and its preceding path segment if and only if the preceding path segment is not slash dot dot slash.<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>srcPath</em> </td><td>The path for which you want to remove the slash dot dot slash sequence and its preceding path segment. </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>manager</em> </td><td>The <aclass="el"href="classxercesc_1_1MemoryManager.html">MemoryManager</a> to use to allocate objects </td></tr>
To remove the sequence, dot slash if it is part of the sequence, slash dot slash.<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>srcPath</em> </td><td>The path for which you want to remove the dot slash sequence. </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>manager</em> </td><td>The <aclass="el"href="classxercesc_1_1MemoryManager.html">MemoryManager</a> to use to allocate objects </td></tr>
This must be implemented by the per-platform driver which will use local file services to reset the file position to the start of the the file.<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>theFile</em> </td><td>The file handle that you want to reset </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>manager</em> </td><td>The <aclass="el"href="classxercesc_1_1MemoryManager.html">MemoryManager</a> to use to allocate objects </td></tr>
This function enables/disables strict IANA encoding names checking.
<p>
The strict checking is disabled by default.<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>state</em> </td><td>If true, a strict IANA encoding name check is performed, otherwise, no checking. </td></tr>
The termination call is currently optional, to aid those dynamically loading the parser to clean up before exit, or to avoid spurious reports from leak detectors. </td>
Each per-platform driver must implement this. Only it knows what the actual content of the passed mutex handle is.<p>
Note that, since the underlying system synchronization services are used, Xerces cannot guarantee that lock/unlock operations are correctly enforced on a per-thread basis or that incorrect nesting of lock/unlock operations will be caught.<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>mtxHandle</em> </td><td>The mutex handle that you want to unlock </td></tr>
This must be implemented by the per-platform driver, and should weave the relative path part together with the base part and return a new path that represents this combination.<p>
If the relative part turns out to be fully qualified, it will be returned as is. If it is not, then it will be woven onto the passed base path, by removing one path component for each leading "../" (or whatever is the equivalent in the local system) in the relative path.<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>basePath</em> </td><td>The string containing the base path </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>relativePath</em> </td><td>The string containing the relative path </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>manager</em> </td><td>The <aclass="el"href="classxercesc_1_1MemoryManager.html">MemoryManager</a> to use to allocate objects </td></tr>
</table>
</dl>
<dlcompact><dt><b>Returns:</b></dt><dd>Returns a string containing the 'woven' path. It should be dynamically allocated and becomes the responsibility of the caller to delete. </dd></dl>
This must be implemented by the per-platform driver, which should use local file services to write up to 'toWrite' bytes of data to the passed file. Unless exception raised by local file services, 'toWrite' bytes of data is to be written to the passed file.<p>
<dlcompact><dt><b>Parameters:</b></dt><dd>
<tableborder="0"cellspacing="2"cellpadding="0">
<tr><tdvalign="top"></td><tdvalign="top"><em>theFile</em> </td><td>The file handle to be written to. </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>toWrite</em> </td><td>The maximum number of byte to write from the current position </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>toFlush</em> </td><td>The byte buffer to flush </td></tr>
<tr><tdvalign="top"></td><tdvalign="top"><em>manager</em> </td><td>The <aclass="el"href="classxercesc_1_1MemoryManager.html">MemoryManager</a> to use to allocate objects </td></tr>
This memory manager always allocates memory by calling the global new[] operator. It may be used to allocate memory where such memory needs to be deletable by calling delete []. Since this allocator is always guaranteed to do the same thing there is no reason, nor facility, to override it. </td>
This is provided by the per-platform driver, so each platform can choose what actual implementation it wants to use. The object must be dynamically allocated.<p>
<em>Note that you may optionally, if your platform driver does not install a network accessor, set it manually from your client code after calling <aclass="el"href="classxercesc_1_1XMLPlatformUtils.html#f72fdf4110e3458cbf5f7f6b108f8d06">Initialize()</a>. This works because this object is not required during initialization, and only comes into play during actual XML parsing.</em></td>
This is provided by the per platform driver, so each platform can choose what implemenation it wants to use. When the platform independent initialization code needs to get a transcoding service object, it will call <code>makeTransService()</code> to ask the per-platform code to create one. Only one transcoding service object is reqeusted per-process, so it is shared and synchronized among parser instances within that process. </td>
