X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fdeveloper-manual%2Findex.html;h=ee094afb6e667b78d8cbeea9b3ce2d1342628bc6;hp=29fdc7189ea4f2e6b9f2d5ac200f32fe97542f83;hb=9def9517abf9440ecd38685ccd2aaa3638432084;hpb=5fd77903894c0798908743d90ce72b9bdf2cce7d diff --git a/doc/webserver/developer-manual/index.html b/doc/webserver/developer-manual/index.html index 29fdc718..ee094afb 100644 --- a/doc/webserver/developer-manual/index.html +++ b/doc/webserver/developer-manual/index.html @@ -9,56 +9,52 @@ - - +

Privoxy Developer Manual

-

Copyright © - 2001-2009 by Privoxy +

Copyright © 2001-2016 by Privoxy Developers

-

$Id: developer-manual.sgml,v 2.39 2012/03/18 - 01:16:35 diem Exp $

- -
- - -

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.

- -

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

+

$Id: developer-manual.sgml,v 2.70 2016/05/22 + 12:42:11 fabiankeil Exp $

+ +
+
+ + +

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.

+ +

Please note that this document is constantly evolving. This copy + represents the state at the release of version 3.0.25. You can find + the latest version of the this manual at https://www.privoxy.org/developer-manual/. Please have a + look at the contact section in the user manual if you are interested + in contacting the developers.

+
-
Table of Contents
+
Table of Contents
1. Introduction
@@ -92,7 +88,7 @@ body {
3.2. Privoxy Documentation Style
-
3.3. Privoxy Custom +
3.3. Privoxy Custom Entities
@@ -228,26 +224,23 @@ body {
4.7.3. Try to avoid falling through cases in a switch statement.
-
4.7.4. Use 'long' or 'short' - Instead of 'int'
- -
4.7.5. Don't mix size_t and +
4.7.4. Don't mix size_t and other types
-
4.7.6. Declare each variable +
4.7.5. Declare each variable and struct on its own line.
-
4.7.7. Use malloc/zalloc +
4.7.6. Use malloc/zalloc sparingly
-
4.7.8. The Programmer Who Uses +
4.7.7. The Programmer Who Uses 'malloc' is Responsible for Ensuring 'free'
-
4.7.9. Add loaders to the +
4.7.8. Add loaders to the `file_list' structure and in order
-
4.7.10. "Uncertain" new code - and/or changes to existing code, use FIXME or XXX
+
4.7.9. "Uncertain" new code + and/or changes to existing code, use XXX
@@ -262,9 +255,6 @@ body {
5.1. Testplan for releases
- -
5.2. Test - reports
@@ -309,15 +299,6 @@ body {
6.3.9. FreeBSD
- -
6.3.10. HP-UX - 11
- -
6.3.11. Amiga - OS
- -
6.3.12. AIX
@@ -330,54 +311,12 @@ body {
7. Update the Webserver
- -
8. Contacting the developers, Bug - Reporting and Feature Requests
- -
-
-
8.1. Get - Support
- -
8.2. Reporting - Problems
- -
-
-
8.2.1. Reporting Ads - or Other Configuration Problems
- -
8.2.2. Reporting - Bugs
-
-
- -
8.3. Request New - Features
- -
8.4. Mailing - Lists
-
-
- -
9. Privoxy Copyright, License and - History
- -
-
-
9.1. License
- -
9.2. History
-
-
- -
10. See also
-
+