[#4745] Win32: Ruby & APR; build problems for Ruby Subversion SWIG bindings — Erik Huelsmann <ehuels@...>

Having taken upon me the task to provide a Windows build for

24 messages 2005/04/20
[#4746] Re: Win32: Ruby & APR; build problems for Ruby Subversion SWIG bindings — Austin Ziegler <halostatue@...> 2005/04/20

On 4/20/05, Erik Huelsmann <ehuels@gmail.com> wrote:

[#4747] Re: Win32: Ruby & APR; build problems for Ruby Subversion SWIG bindings — Erik Huelsmann <ehuels@...> 2005/04/20

Hi Austin,

[#4762] Re: Win32: Ruby & APR; build problems for Ruby Subversion SWIG bindings — nobu.nokada@... 2005/04/24

Hi,

[#4783] Re: Win32: Ruby & APR; build problems for Ruby Subversion SWIG bindings — Erik Huelsmann <ehuels@...> 2005/04/25

On 4/24/05, nobu.nokada@softhome.net <nobu.nokada@softhome.net> wrote:

[#4787] Re: Win32: Ruby & APR; build problems for Ruby Subversion SWIG bindings — nobu.nokada@... 2005/04/25

Hi,

[#4794] Re: Win32: Ruby & APR; build problems for Ruby Subversion SWIG bindings — Erik Huelsmann <ehuels@...> 2005/04/25

> > > Ruby is just using AC_TYPE_UID_T. So, using typedef for them,

[#4751] Illegal regexp causes segfault — Andrew Walrond <andrew@...>

irb(main):058:0> a = /\[([^]]*)\]/

13 messages 2005/04/22

Re: Win32: Ruby & APR; build problems for Ruby Subversion SWIG bindings

From: Erik Huelsmann <ehuels@...>
Date: 2005-04-25 09:42:01 UTC
List: ruby-core #4784
On 4/22/05, William A. Rowe, Jr. <wrowe@rowe-clan.net> wrote:
> At 05:23 PM 4/21/2005, Branko Cibej wrote:
> >This, I think, is a classic case of programmers' hubris. We should've defined apr_pid_t &co. on all platforms, not polluted the namespace with names that APR doesn't own (and that will clash with any Windows implementation of a POSIX-like API).
> 
> ++1.
> 
> My last point about the patch to apr.hw to define FD_SETSIZE
> suffers this exact same hubris.
> 
> The quicker we (open source projects, collectively) stop trying
> to enforce the 'one right way' to use posix/win32 etc, the sooner
> these projects will compile (collectively) with one another.

I take that as a signal to go implement apr_pid_t and friends for all
platforms (a patch for thrunk).  Do you have anything you want to
stress before I start the work?


bye,


Erik.


In This Thread