Mailing Lists Posting Guidelines
Please follow these simple guidelines when posting to the mailing lists hosted by Code Synthesis:
- When replying to a message sent to the mailing list, keep the mailing list CC'ed in your reply. This way other subscribers who may have had a similar question can provide you with a solution. Plus, questions and answers will be archived and available to others with similar questions in the future.
- Do not send a new question by replying to an existing message with an unrelated subject since it makes email clients with support for threading as well as the mailing list archives less usable. Instead, create a new email with a new subject.
- Choose a descriptive subject line for your post. Examples of bad subjects: "Question", "Problem", "Help me". Examples of good subjects: "Error compiling generated code for schema Foo with VC++ 7.1", "Problem with inline and type customization".
- If reporting a problem, make sure to specify all the relevant product and environment information, such as product version, operating system name and version, C++ compiler name and version.
- Do not send images with screenshots of errors. Instead, describe what happened in the email. For example: "When trying to run the program, I got the Assertion Failed dialog which indicates that the failure occurred in file test.cxx line 123. The message says Invalid null pointer."
- If sending sample source code, XML documents, or schemas, prefer
to upload the archive on a Web or FTP server somewhere and put
the URL into your post. If you have to attach the archive
to the email, use archive formats for which open-source
decompression tools are available, such as
.zip,.tar.gz, and.tar.bz2. In particular, do not use.rar. Make sure that you do not include generated code, object files, libraries, or executables in your archive.
As an incentive to follow these guidelines, Code Synthesis staff assigns higher priority to questions that do not violate any of the above rules.