SWIG image
Home Github Development Community Support Bugs and Patches
Information
What is SWIG?
Compatibility
Features
Tutorial
Documentation
News
The Bleeding Edge
History
Guilty Parties
Projects
Legal Department
Links
Download
SwigWiki
Survey
Donate
Affiliations
Software Freedom Conservancy logo
Our Generous Host
Get SWIG at SourceForge.net. Fast, secure and Free Open Source software downloads
Exits
C# - Mono
C# - MS .NET
D
Go language
Guile
Java
Javascript - Node.js
Javascript - Node-API
Javascript - V8
Javascript - WebKit
Lua
MzScheme/Racket
OCaml
Octave
Perl
PHP
Python
R
Ruby
Scilab
Tcl/Tk
Community Support

SWIG is an all volunteer project with typical open source community support. There are a number of mailing lists available. These have traditionally been used for any queries related to the use or development of SWIG. The popularity of mailing lists has declined in recent years and many users have started to use Github discussions and Stack Overflow. For general help and support, we suggest you consider one of the following:

  1. Stack Overflow. The link takes you straight to the all the questions with the [swig] tag. You may want to add language tags, such as [ruby], [python] etc to narrow down the scope.
  2. SWIG Github Discussions for discussing any kind of SWIG related topic.
  3. SWIG Github Issues if you have found a bug. Please raise a new issue if you can provide a cut down test case with all the details to recreate it. See Bugs and Patches for more details.
  4. SWIG Github Pull Requests if you would like to contribute a patch to improve SWIG. More details at Bugs and Patches.
  5. The swig-user mailing list for general user queries, more details below.
  6. The swig-devel mailing list for SWIG development related discussions, more details below.
Mailing Lists

The mailing lists are subscriber only lists, so you must subscribe to the relevant list in order to post to that list.

The mailing lists are set with a very high level of spam rejection, meaning occasionally some SWIG user's email postings will be discarded. Emails classified as spam are quietly discarded, so please check the archives if you are unsure as to whether or not your email was successfully posted. Note that plain text emails are preferred as html, rtf etc formatted emails have been known to be quietly discarded.

To subscribe to any of the mailing lists or view the archives, use the links on the left column.

List Purpose
swig-user General discussion and queries about SWIG for users.
swig-devel Discussion list for SWIG developers or anyone interested in SWIG development.
swig-cvs SWIG Github commits list. A summary of Git commits are mailed to this list. The list name is a historical relic from when we used CVS for revision control. The list also contains historic Subversion commits.

Note that these mailing lists began use in November 2005 and replaced the older original mailing lists. Details of searching or browsing both the current and original lists are given below.

Top posting and bottom posting

Replies to emails can be either bottom or top posted. The SWIG community by and large uses bottom postings or inline replies. This doesn't mean top postings are ruled out, however, an email chain with both top and bottom postings is rather difficult to follow and should be avoided. Please don't mix top and bottom posts in one thread, stick with whichever approach the first reply used.

For those who are new to mailing lists, there are many articles on the subject, for example, Bottom vs. top posting and quotation style on Usenet.

Searching and browsing the mailing lists archives

The current SourceForge mailing lists began use towards the end of 2005 and are listed below.

swig-user archives
swig-devel archives
swig-cvs archives

The lists at Sourceforge can be searched directly on the Sourceforge SWIG mailing lists page.

The original mailing lists in use prior to November 2005 were hosted at the University of Chicago, but are no longer accessible using the original links.

swig archives - swig-user equivalent
swig-dev archives - swig-devel equivalent

However, these original mailing lists are partially archived by Gmane and include emails from around the year 2000 and later. Gmane combines the original equivalent and current mailing lists as described below. They can be read using an NNTP newsreader configured to use server news.gmane.io and the groups listed in the following table.

Group Mailing lists
gmane.comp.programming.swig Combination of the original swig and current swig-user mailing lists
gmane.comp.programming.swig.devel Combination of the original swig-dev and current swig-devel mailing lists


Feedback and questions regarding this website as well as patches for improvement should be raised on the SWIG www Github project.

Last modified : Wed Nov 27 19:02:45 2024