Re: Same name of function argument and variable name

Tamal Saha wrote:
> Hi,
> I am using SWIG 1.3.39 to generate C# wrapper of UW IMAP toolkit. The 
> problem is that 2 auto generated function have the signature as following:
> 
>   public static search_set mail_parse_set(string s, SWIGTYPE_p_p_char ret) {
>     IntPtr cPtr = LibcclientPINVOKE.mail_parse_set(s, 
> SWIGTYPE_p_p_char.getCPtr(ret));
>     search_set ret = (cPtr == IntPtr.Zero) ? null : new search_set(cPtr, 
> false);
>     return ret;
>   }
> 
>   public static uint mail_strip_subject(string t, SWIGTYPE_p_p_char ret) {
>     uint ret = LibcclientPINVOKE.mail_strip_subject(t, 
> SWIGTYPE_p_p_char.getCPtr(ret));
>     return ret;
>   }
> 
> What is the possible solution? 
> 
A few suggestions, shown just for mail_parse_set and assuming this C 
method being wrapped is declared as:
   search_set * mail_parse_set(const char *s, char **ret);
and assuming it is defined in xx.h header

1) redefine the method giving a new parameter name or dropping the name:
search_set mail_parse_set(const char *s, char **);
%ignore mail_parse_set;
%include "xx.h"

New Project Announcement: SWIG Starter Kit

I noticed that each time I went to use SWIG in a new project I was
writing some of the same boiler plate C++ and autoconf code. So, I
created the Swig Starter Kit to help myself and others get started.
It's pretty basic right now, but much more is in the works. The
project is not brand new, but I did just notice the list of projects
using SWIG recently (http://www.swig.org/projects.html) and was hoping
I might get the Swig Starter Kit added to the list.

The code is MIT - style license, meant to be very free for commercial
and non-commercial use.

The google code page: http://swigstarterkit.googlecode.com
General news and announcements page: http://blog.emptycrate.com/taxonomy/term/77

Thank you,
Jason

--

-- 
http://emptycrate.com Games, Programming, Travel & other stuff

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf

Delphi/Pascal Module

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf

Building swig on cygwin

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf

Re: Delphi/Pascal Module

Stefano Moratto wrote:
> William,
>            I had some problem with gmail, I responded to you but the
> mail was not delivered.
>
> I'm very glad to test codestriker for submit the patch.
>
> I was thinking about the name of the module: the FreePascal community is
> growing and this module may be appealing to them.
> I would like to rename the module in Pascal instead of Delphi.
>
> Is better to rename it before the patch submission?
>
Stefano

It would be great if you could target both the free pascal compiler as 
well as Delphi. As SWIG is an open source project, free/open source 
targets are preferrable to proprietary. I presume you can get it to work 
with both? Anyway, I'd rather see the patch with the final name than one 
that is going to change.

William

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf

Re: Building swig on cygwin

Stefano Moratto wrote:
> Hello,
>          I checkout the repository's head using SVN for windows (Tortoise)
> 
> When I run autogen.sh from the cygwin bash shell I get the errors:
> 
> $ ./autogen.sh
> ./autogen.sh: line 2: $'\r': command not found
> ./autogen.sh: line 7: $'\r': command not found
> : invalid optionne 8: set: -
> set: usage: set [--abefhkmnptuvxBCHP] [-o option] [arg ...]
> 
> may it be related to the "\n" difference between Unix and Windows?
> 
I use the cygwin version of svn and there don't get any problems, 
although my cut of cygwin is fairly old now. Perhaps you've got Tortoise 
to convert to Windows line endings? The svn:eol-style property is not 
set in autogen.sh so it probably defaults to whatever the client is 
configured to.

William

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf

svn access for summer of code students

I've set up a developer accounts for all of the summer of code students. 
You should all be able to check into svn now. Please create a branch for 
doing your development work (except Kosei who is using the Xapian repo). 
I suggest calling your branches gsoc2009-xxx, where xxx is your SF 
account name.

For now, please create your branch and make a simple commit, for 
example, add your name/email into the README file so that we know you 
are up and running ready to start commiting when coding starts on 23 
May. Please also subscribe to the swig-cvs mailing list, so you can 
track your own commits as well as others. Maybe it is a bit confusing, 
as the mailing list name contains cvs, but the swig-cvs mailing list is 
used for svn commits!

Make sure you use a subversion 1.5 or higher client for when you do 
merging. This is quite important, else the merge info doesn't work 
properly as subversion underwent some big merging improvements in 1.5. 
Although, I can't see how to verify this, the SF svn server now seems to 
use version 1.5 
(http://apps.sourceforge.net/trac/sourceforge/wiki/Subversion), so we 
can use the improved svn merging. Previously we used svnmerge.py for 
merging, but this should no longer be necessary. We're hoping your work 
will be in a good enough state at the end of the coding period to then 
merge back into trunk for release to the general public. I therefor 
suggest you all merge from svn trunk to your branch regularly because if 
you don't merge regularly, merging can start to get rather complicated 
and messy.

Cheers
William

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf

Re: svn access for summer of code students

On Mon, May 04, 2009 at 09:30:58PM +0100, William S Fulton <wsf <at> fultondesigns.co.uk> wrote:
> I've set up a developer accounts for all of the summer of code students. 
> You should all be able to check into svn now. Please create a branch for 
> doing your development work (except Kosei who is using the Xapian repo). 
> I suggest calling your branches gsoc2009-xxx, where xxx is your SF 
> account name.
> 
> For now, please create your branch and make a simple commit, for 
> example, add your name/email into the README file so that we know you 
> are up and running ready to start commiting when coding starts on 23 
> May.

I've did an

$ svn copy https://swig.svn.sourceforge.net/svnroot/swig/trunk \
        https://swig.svn.sourceforge.net/svnroot/swig/branches/gsoc2009-vmiklos \
        -m "Making Miklos' GSoC Branch"

> Please also subscribe to the swig-cvs mailing list, so you can 
> track your own commits as well as others. Maybe it is a bit confusing, 
> as the mailing list name contains cvs, but the swig-cvs mailing list is 
> used for svn commits!

Ugh, I did it in the wrong order, I subscribed after committing, so the
mail generated from my commit is now pending, sorry for that.

> 
> Make sure you use a subversion 1.5 or higher client for when you do 
> merging. This is quite important, else the merge info doesn't work 
> properly as subversion underwent some big merging improvements in 1.5. 
> Although, I can't see how to verify this, the SF svn server now seems to 
> use version 1.5 
> (http://apps.sourceforge.net/trac/sourceforge/wiki/Subversion), so we 
> can use the improved svn merging. Previously we used svnmerge.py for 
> merging, but this should no longer be necessary.

Ok, using 1.5.4.

> We're hoping your work will be in a good enough state at the end of
> the coding period to then merge back into trunk for release to the
> general public. I therefor suggest you all merge from svn trunk to
> your branch regularly because if you don't merge regularly, merging
> can start to get rather complicated and messy.

What is the recommended interval? I would imagine that we work on our
project, and once it is in a reasonable shape (so we both have the
necessary code and unit tests done), we can also merge trunk to your
branch and resolve conflicts if there are any. Is this a bad idea and
should we merge for example each day? In that case we'll see smaller
conflicts but we won't have a clean history because of big number of
unnecessary merges.

Thanks.

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf

Re: svn access for summer of code students

Miklos Vajna wrote:
> Ugh, I did it in the wrong order, I subscribed after committing, so the
> mail generated from my commit is now pending, sorry for that.
> 
Okay, no problem, I've approved this mail onto the list.

> What is the recommended interval? I would imagine that we work on our
> project, and once it is in a reasonable shape (so we both have the
> necessary code and unit tests done), we can also merge trunk to your
> branch and resolve conflicts if there are any. Is this a bad idea and
> should we merge for example each day? In that case we'll see smaller
> conflicts but we won't have a clean history because of big number of
> unnecessary merges.
Not much happening right now on trunk, so it depends on the activity and 
when it picks up. You can see the activity by monitoring the mailing 
list and make your judgement. The main advice is the more often you 
merge the easier it is, but do it within reason. Probably weekly merges 
from trunk is the best balance.

William

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf

Re: svn access for summer of code students

在 2009-05-04一的 21:30 +0100，William S Fulton写道：
> I've set up a developer accounts for all of the summer of code students. 
> You should all be able to check into svn now. Please create a branch for 
> doing your development work (except Kosei who is using the Xapian repo). 
> I suggest calling your branches gsoc2009-xxx, where xxx is your SF 
> account name.

I have added one:
https://swig.svn.sourceforge.net/svnroot/swig/branches/gsoc2009-sploving/

> For now, please create your branch and make a simple commit, for 
> example, add your name/email into the README file so that we know you 
> are up and running ready to start commiting when coding starts on 23 
> May. Please also subscribe to the swig-cvs mailing list, so you can 
> track your own commits as well as others. Maybe it is a bit confusing, 
> as the mailing list name contains cvs, but the swig-cvs mailing list is 
> used for svn commits!

I have added my name and email into the README:
 $ svn commit -m "adding my information in README"

> Make sure you use a subversion 1.5 or higher client for when you do 
> merging. This is quite important, else the merge info doesn't work 
> properly as subversion underwent some big merging improvements in 1.5. 
> Although, I can't see how to verify this, the SF svn server now seems to 
> use version 1.5 
> (http://apps.sourceforge.net/trac/sourceforge/wiki/Subversion), so we 
> can use the improved svn merging. Previously we used svnmerge.py for 
> merging, but this should no longer be necessary. We're hoping your work 
> will be in a good enough state at the end of the coding period to then 
> merge back into trunk for release to the general public. I therefor 
> suggest you all merge from svn trunk to your branch regularly because if 
> you don't merge regularly, merging can start to get rather complicated 
> and messy.

My svn is 1.3, but I will update it later to subversion 1.5 when 
necessary.

Best wishes

> Cheers
> William
> 
> ------------------------------------------------------------------------------
> Register Now & Save for Velocity, the Web Performance & Operations 
> Conference from O'Reilly Media. Velocity features a full day of 
> expert-led, hands-on workshops and two days of sessions from industry 
> leaders in dedicated Performance & Operations tracks. Use code vel09scf 
> and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
> _______________________________________________
> Swig-devel mailing list
> Swig-devel <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/swig-devel

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Swig-devel mailing list
Swig-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/swig-devel