[#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: [PATCH] tempfile.rb

From: Tilman Sauerbeck <tilman@...>
Date: 2005-04-25 14:37:07 UTC
List: ruby-core #4789
nobu.nokada@softhome.net <nobu.nokada@softhome.net> [2005-04-25 23:27]:
> At Mon, 25 Apr 2005 23:01:37 +0900,
> Tilman Sauerbeck wrote in [ruby-core:04786]:
> > > This was then fixed in CVS by making Tempfile#_close only set @data[1]
> > > to nil if @data isn't nil.
> > > 
> > > I suspect that this isn't the right way to fix it, maybe it's better to
> > > only set @data[1] to nil instead of @data in #unlink (and #close!)?
> > > 
> > > Attached a diff against CVS HEAD.
> 
> Your example worked fine with 1.9, so it should be backported
> from HEAD to 1.8, not patching against HEAD?

My point is that the code in HEAD looks suspicious, so I sent in a better
patch to fix the problem.

But yes, the original fix (and my patch probably) need to be backported
to 1.8.

-- 
Regards,
Tilman

In This Thread

Prev Next