Privoxy Developer Manual

The developer manual gives the users information on how to help the developer - team. It provides guidance on coding, testing, documentation and other - issues. -

The developer manual provides guidance on coding, testing, packaging, documentation + and other issues of importance to those involved with + Privoxy development. It is mandatory (and helpful!) reading + for anyone who wants to join the team. Note that it's currently out of date + and may not be entirely correct. As always, patches are welcome.

You can find the latest version of the this manual at Please note that this document is constantly evolving. This copy represents + the state at the release of version 3.0.27. + You can find the latest version of the this manual at http://www.privoxy.org/developer-manual/https://www.privoxy.org/developer-manual/. - Please see the Contact section - on how to contact the developers.

contact section in the user manual + if you are interested in contacting the developers.

2.2. CVS Commit GuidelineBranches

2.3. Discussing Changes FirstCVS Commit Guidelines

3.3. Privoxy Custom Entities

4.7.4. Use 'long' or 'short' Instead of - 'int'

4.7.5. Don't mix size_t and other types

4.7.6. 4.7.5. Declare each variable and struct on its own line.

4.7.7. 4.7.6. Use malloc/zalloc sparingly

4.7.8. 4.7.7. The Programmer Who Uses 'malloc' is Responsible for Ensuring 'free'

4.7.9. 4.7.8. Add loaders to the `file_list' structure and in order

4.7.10. 4.7.9. "Uncertain" new code and/or changes to - existing code, use FIXME