headers
David Beazley | 2 Jun 2005 03:51
Favicon

Well, I guess this is it...


I just taught my last lecture as a University professor today.  As
many of you know, I am getting out of the whole academic game so
things are in transition at the moment (the major reason why I have
been so inactive on SWIG development lately).   That said, I wanted to 
give everyone a heads up on a few developments.

-  I have relocated the SWIG Wiki to a new personal web site.
   (www.dabeaz.com).   However, ever since the Wiki got inundated with 
   spam, it's been a little flaky.   I'm thinking about reorganizing
   it as some kind of FAQ when inspiration strikes.    Alternatively,
   if anyone has ideas on how to improve this, let me know.

-  At some point, I think we need to relocate the
   "swig <at> cs.uchicago.edu" and "swig-dev <at> cs.uchicago.edu" mailing
   lists.    Given the maintenance/spam nightmare of these
   lists, I really don't want to be the administrator if it means
   that I'm the one doing all of the moderation/filtering of posts.
   My first inclination is to just move the lists over to a major service
   provider like Yahoo.   We wouldn't be the only open-source project
   with such an arrangement.   Comments?

-  I am going to continue to be AWOL on SWIG development in the near
   future. After suffering through academic hell for the last few
   years, I'm going to be taking a personal sabatical to just chill
   out for awhile.  See the note (*) below for details.

I've only caught bits and pieces of recent conversions.  Here are a few
random comments:
(Continue reading)

Permalink | Reply | 9 comments |
headers
Bill Clarke | 2 Jun 2005 04:07
Picon
Favicon

Re: Well, I guess this is it...

David Beazley wrote, On 06/02/05 11:51:
> I just taught my last lecture as a University professor today.  As
> many of you know, I am getting out of the whole academic game so
> things are in transition at the moment (the major reason why I have
> been so inactive on SWIG development lately).   That said, I wanted to 
> give everyone a heads up on a few developments.

i'm sure i'm speaking for everyone when i say, thanks for all the great
work you've done in the past, we all appreciate it.  and i personally
hope you can keep working on SWIG or whatever else grabs your interest.

i'm sure you deserve a break, make the best of it!

> -  At some point, I think we need to relocate the
>    "swig <at> cs.uchicago.edu" and "swig-dev <at> cs.uchicago.edu" mailing
>    lists.    Given the maintenance/spam nightmare of these
>    lists, I really don't want to be the administrator if it means
>    that I'm the one doing all of the moderation/filtering of posts.
>    My first inclination is to just move the lists over to a major service
>    provider like Yahoo.   We wouldn't be the only open-source project
>    with such an arrangement.   Comments?

i've been happy with yahoo groups.  it works.
what about sourceforge?  (the archives are rather annoying on
sourceforge though)

-

if you ever come to canberra, i'd be happy to organise something.
there's a few SWIG users here who i'm sure would be happy to buy you
(Continue reading)

Permalink | Reply | 6 comments |
headers
Chris Miller | 2 Jun 2005 04:37
Favicon

The php thing

Hello,
    I'm attempting to use the PHP functionality in Swig. As many others 
before me have posted, the example code (or any code for that matter) 
will not produce a module that PHP recognizes. In addition, the modules 
produced lack the "php_" prefix that is specified in the example.php 
script that is generated. I've tried swig 1.3.21 under Fedora Core 3, 
and FreeBSD 4.11, as well as downloaded and compiled swig 1.3.24 under 
Fedora, no luck. I read a while back that the maintainer of the PHP code 
is AWOL, but  I suspect that it worked once upon a time. Can someone 
confirm this is a known problem (nothing in the bug database) and/or 
provide any clues as how I can get this feature to work? Below is the 
output of my attempt per the docs. Thanks in advance.

Regards,
    Chris

[root <at> turbo swig]# cat example.i
%module example

#define TEST    Hello
#define Test    World

[root <at> turbo swig]# swig -php4 -phpfull example.i

[root <at> turbo swig]# phpize
Configuring for:
PHP Api Version:         20020918
Zend Module Api No:      20020429
Zend Extension Api No:   20021010
(Continue reading)

Permalink | Reply | 0 comments |
headers
David Beazley | 2 Jun 2005 05:59
Favicon

Re: Well, I guess this is it...

Bill Clarke writes:
 > 
 > > -  At some point, I think we need to relocate the
 > >    "swig <at> cs.uchicago.edu" and "swig-dev <at> cs.uchicago.edu" mailing
 > >    lists.    Given the maintenance/spam nightmare of these
 > >    lists, I really don't want to be the administrator if it means
 > >    that I'm the one doing all of the moderation/filtering of posts.
 > >    My first inclination is to just move the lists over to a major service
 > >    provider like Yahoo.   We wouldn't be the only open-source project
 > >    with such an arrangement.   Comments?
 > 
 > i've been happy with yahoo groups.  it works.
 > what about sourceforge?  (the archives are rather annoying on
 > sourceforge though)
 > 

My only complain with SourceForge is that the lists are also based on
mailman.  Given the amount of spam and the way that mailman
administration works, I'm not sure I really want to go that route.

I have to say that I've been really happy with my Yahoo email
account.   The spam filtering is significantly better than my
university account---so much so that I don't really have to worry
about it much.   If the groups are similar, that might be a good
option.  Actually, anything that requires very little effort on our
part is good ;-).

 > if you ever come to canberra, i'd be happy to organise something.
 > there's a few SWIG users here who i'm sure would be happy to buy you
 > many beers.
(Continue reading)

Permalink | Reply | 5 comments |
headers
Jason E. Stewart | 2 Jun 2005 07:25

Re: Well, I guess this is it...

David Beazley <beazley <at> cs.uchicago.edu> writes:

> My only complain with SourceForge is that the lists are also based on
> mailman.  Given the amount of spam and the way that mailman
> administration works, I'm not sure I really want to go that route.

Hey Dave,

I thought I would share my personal experience managing lists for two
different groups, one set on SF the other at Apache. I hope they are
useful.

Here's my experience:

I maintain around 10 mailing lists on SF, and I also maintain two
lists for apache. 

Apache
--

Apache uses ezmlm to do their lists - the lists are moderated, so I
get moderator emails evertime someone not subscribed sends mail. For
the two lists I get about 10 emails/day and usually 1 or 2 out of 10
are real, the rest are SPAM. To approve the non-spam I just send a
blank reply back to ezmlm and it takes care of the rest.

It's pretty simple - the moderator email contains the text of the
posting, so I can see right away if it's real or spam, if it's spam I
do nothing and ezmlm deletes it in a week.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Prabhu Ramachandran | 2 Jun 2005 09:20

Re: Well, I guess this is it...

>>>>> "Jason" == Jason E Stewart <jason <at> openinformatics.com> writes:

    Jason> David Beazley <beazley <at> cs.uchicago.edu> writes:
    >> My only complain with SourceForge is that the lists are also
    >> based on mailman.  Given the amount of spam and the way that
    >> mailman administration works, I'm not sure I really want to go
    >> that route.

    >> From the 10 lists I maintain I get around 20 emails/day. Only
    >> about 4
    Jason> emails per *week* or real - the rest are SPAM.

    Jason> If the emails are real I need to log into the admin page on
    Jason> SF, and approve the real emails. For the SPAM, I do nothing
    Jason> and SF cleans them up in about 5 days.
[...]
    Jason> Because my SF lists don't get many posts from
    Jason> non-subscribers, it is relatively low hassle. I suspect
    Jason> SWIG and SWIG-DEV would require more action, and that would
    Jason> be more work. With mailman it is also possible to add
    Jason> addresses to the pre-approved list - but you have to do it
    Jason> manually using the point-and-click web interface - and that
    Jason> is too much effort.

Well, that is true of older versions of mailman which SF runs.  With
Mailman 2.x (certainly with 2.1.2), you can check an option to
accept/reject/hold/discard addresses *as you moderate* the posts.  I
have no idea when SF will upgrade their version of Mailman though.

    Jason> I've found that both apache and SF have *very* good SPAM
(Continue reading)

Permalink | Reply | 0 comments |
headers
Thien-Thi Nguyen | 2 Jun 2005 14:37

Re: Well, I guess this is it...

David Beazley <beazley <at> cs.uchicago.edu> writes:

> (i.e., working as an unemployed slacker)

this is a lot of fun -- i recommend it to anyone who can manage it!

> cool to meet a few more of
> the SWIG hackers

argh, i can't in good conscience call myself a SWIG hacker anymore.
however, if you ever find yourself tooling around between milano and
torino, feel free to ping me (a little in advance so i can plan my
slacker schedule :-) for local sudsing.

thi
Permalink | Reply | 1 comment |
headers
William S Fulton | 3 Jun 2005 00:36
Picon
Favicon
Gravatar

Re: Well, I guess this is it...

David Beazley wrote:
> Bill Clarke writes:
>  > 
>  > > -  At some point, I think we need to relocate the
>  > >    "swig <at> cs.uchicago.edu" and "swig-dev <at> cs.uchicago.edu" mailing
>  > >    lists.    Given the maintenance/spam nightmare of these
>  > >    lists, I really don't want to be the administrator if it means
>  > >    that I'm the one doing all of the moderation/filtering of posts.
>  > >    My first inclination is to just move the lists over to a major service
>  > >    provider like Yahoo.   We wouldn't be the only open-source project
>  > >    with such an arrangement.   Comments?
>  > 
>  > i've been happy with yahoo groups.  it works.
>  > what about sourceforge?  (the archives are rather annoying on
>  > sourceforge though)
>  > 
> 
> My only complain with SourceForge is that the lists are also based on
> mailman.  Given the amount of spam and the way that mailman
> administration works, I'm not sure I really want to go that route.
> 
> I have to say that I've been really happy with my Yahoo email
> account.   The spam filtering is significantly better than my
> university account---so much so that I don't really have to worry
> about it much.   If the groups are similar, that might be a good
> option.  Actually, anything that requires very little effort on our
> part is good ;-).
> 

The SWIG developers can help with the mailing list administration, I for
(Continue reading)

Permalink | Reply | 2 comments |
headers
Luigi Ballabio | 3 Jun 2005 09:44
Picon

Re: Well, I guess this is it...


On 06/02/2005 02:37:16 PM, Thien-Thi Nguyen wrote:
> 
> argh, i can't in good conscience call myself a SWIG hacker anymore.
> however, if you ever find yourself tooling around between milano and
> torino, feel free to ping me (a little in advance so i can plan my
> slacker schedule :-) for local sudsing.

Dave,
	if you get to Milano you'll catch both of us.

Cheers,
	Luigi

----------------------------------------

There is no such thing as public opinion. There is only published  
opinion.
-- Winston Churchill
Permalink | Reply | 0 comments |
headers
William S Fulton | 4 Jun 2005 02:04
Picon
Favicon
Gravatar

SWIG-1.3.25 release candidate 1

A release candidate for SWIG-1.3.25 is online at

    http://www.swig.org/swig-1.3.25rc1.tar.gz (Unix source)
    http://www.swig.org/swigwin-1.3.25rc1.zip (Windows)

Please let us know if there are any last minute problems we need to
fix. Assuming no disasters we aim to make the official release in one 
weeks time.

William

SWIG-1.3.25 summary:
- Improved runtime type system.  Speed of module loading improved in
   modules with lots of types.  SWIG_RUNTIME_VERSION has been increased
   from 1 to 2, but the API is exactly the same; only internal changes
   were made.
- The languages that use the runtime type system now support external
   access to the runtime type system.
- Various improvements with typemaps and template handling.
- Fewer warnings in generated code.
- Improved colour documentation.
- Many C# module improvements (exception handling, prevention of early
   garbage collection, C# attributes support added, more flexible type
   marshalling/asymmetric types.)
- Minor improvements and bug fixes specific to the C#, Java, TCL, Guile,
   Chicken, MzScheme, Perl, Php, Python, Ruby and Ocaml modules).
- Various other bug fixes and memory leak fixes.
_______________________________________________
Swig maillist  -  Swig <at> cs.uchicago.edu
http://mailman.cs.uchicago.edu/mailman/listinfo/swig
(Continue reading)

Permalink | Reply | 0 comments |

Gmane