Str Library no-nonsense support policy

We will analyze and help you with any issues directly related to Str Library. Some examples are:

• Installation or setup issues; all problems of type "the library does not compile" on various platforms. However, we cannot promise that we can port Str Library for you to a significantly different platform or compiler
• All malfunctions that can be attributed to the library performing incorrectly with correct input parameters
• Missing / incorrect documentation issues
• "How do I" type questions concerning string manupulation with Str Library methods

We cannot help you with:

• The rest of your program (you cannot imagine how often requests of this type pop up!)
• "How do I" questions that do not have a direct relation to the library. A fine real-world example we received was "how do I write a C++ source parser?" - this type of request calls for a consultancy engagement
• Remotely debugging your application or analyzing its trace output to determine whether a problem really lies with Str Library. If you believe you have found a bug with the library, you will have to isolate it and send us a repro (a reproduction scenario)
• All kinds of problems related to exceptions and/or Windows General Protection faults that seem to occur within Str Library source, but cannot be reproduced. Our experience shows that if an issue of this kind cannot be repro-ed, it usually lies with bad pointers in the rest of the application.

Remember, if you find a genuine defect (a feature not performing as documented, or causing exceptions, etc) we will not count the incident at all; and we will work to send you a hotfix (or, at worst, a workaround) as soon as possible.