Null Entity Resolver
Published on 30 Jan 2005Instead of permitting the XML parser to download document type definitions, this entity resolver returns an empty string for all entities.
Instead of permitting the XML parser to download document type definitions, this entity resolver returns an empty string for all entities.
If you have for some reason started out with separate subversion repositories for different aspects of your project but realized that this setup does not make sense anymore, you can use the following instructions to merge repositories.
Although many linux distributions are preconfigured for various locales, they may need further user customization to support the desired features.
Although java.lang.Object declares and implements a method finalize() which is meant to be called by the garbage collector to allow the object to gain control one last time to free resources and finish sanely, I found out in a rather painful way that finalize() will only be called by the garbage collector and not when exiting the program. This means that all the objects that have been in use shortly before shutdown of the virtual machine do not get the chance to close sanely.
To ensure that URLs can be displayed regardless of the locale, special characters are substituted by a percent sign followed by their two digit hexadecimal equivalent.
Regular expressions can easily be documented which is demonstrated in the following example matching floating point numbers:
In one of my projects I needed to process XML files with document type definitions (DTD). The first couple of attempt failed miserably. But after some research I managed to cope:
In addition to the commonly known properties of a statistic, a special analysis of the data can be performed based on the type of the individual values:
The internal variable INPUT_RECORD_SEPARATOR determines which string of characters closes a line of input data.
Although regular expressions are a complex but extremely useful tool for the analysis of strings, they are based on fuzzy logic and, therefore, have high computational demands. Although there can be no universal statement, some rules of thumb can be compiled to support a case-to-case decision whether simple string analysis based on index(), substr(), chr() and ord() is able to improve the time complexity of a perl script with respect to regular expressions.