[#8136] Confused exception handling in Continuation Context — "Robert Dober" <robert.dober@...>

Hi all

13 messages 2006/07/06

[#8248] One-Click Installer: MinGW? or VC2005? — "Curt Hibbs" <ml.chibbs@...>

I just posted this to ruby-talk. But I would also like to discuss this

33 messages 2006/07/18
[#8264] Re: One-Click Installer: MinGW? or VC2005? — Charlie Savage <cfis@...> 2006/07/19

From my experience using both tool chains on Windows (for the ruby-prof

[#8266] Re: One-Click Installer: MinGW? or VC2005? — "Curt Hibbs" <ml.chibbs@...> 2006/07/19

Tim, I'm going to top reply since your post was so long. I'm interested in

[#8267] Re: One-Click Installer: MinGW? or VC2005? — Charlie Savage <cfis@...> 2006/07/19

> Tim, I'm going to top reply since your post was so long. I'm interested in

[#8271] my sandboxing extension!! — why the lucky stiff <ruby-core@...>

I have (what feels like) very exciting news. I finally sat down to code up my

17 messages 2006/07/19

[#8430] Re: doc patch: weakref. — "Berger, Daniel" <Daniel.Berger@...>

> -----Original Message-----

19 messages 2006/07/28
[#8434] Re: doc patch: weakref. — Yukihiro Matsumoto <matz@...> 2006/07/29

Hi,

[#8436] Re: doc patch: weakref. — Daniel Berger <djberg96@...> 2006/07/29

Yukihiro Matsumoto wrote:

[#8437] Re: doc patch: weakref. — Mauricio Fernandez <mfp@...> 2006/07/29

On Sat, Jul 29, 2006 at 07:37:24PM +0900, Daniel Berger wrote:

[#8441] Inconsistency in scoping during module_eval? — "Charles O Nutter" <headius@...>

I have the following code:

18 messages 2006/07/30
[#8442] Re: Inconsistency in scoping during module_eval? — nobu@... 2006/07/30

Hi,

[#8443] Re: Inconsistency in scoping during module_eval? — "Charles O Nutter" <headius@...> 2006/07/30

Why does this:

[#8445] Re: Inconsistency in scoping during module_eval? — Yukihiro Matsumoto <matz@...> 2006/07/30

Hi,

[#8454] Re: Inconsistency in scoping during module_eval? — "Charles O Nutter" <headius@...> 2006/07/31

So to clarify...

Re: Ruby 1.8.5 stable, Process::RLIM_SAVED_CUR issue

From: nobu@...
Date: 2006-07-14 16:51:17 UTC
List: ruby-core #8227
Hi,

At Sat, 15 Jul 2006 01:20:34 +0900,
Daniel Berger wrote in [ruby-core:08224]:
> Looking in limits.h, I see this:
> /* Maximum value an `unsigned long int' can hold.  (Minimum is 0.)  */
> #  if __WORDSIZE == 64
> #   define ULONG_MAX    18446744073709551615UL
> #  else
> #   define ULONG_MAX    4294967295UL
> #  endif
> 
> So, somehow Ruby picked up the 64 bit value.  I *am* on an AMD 64 laptop
> here, btw.  Maybe gcc is doing something funky, but attempting to
> explicitly build with -m64 fails.  It tells me 64 bits support was not
> builtin to the version of gcc that I have.  Here's the result of gcc -v:

You should see bits/resources.h.  If large file support is
enabled, rlim_t will be defined as __rlim64_t.

-- 
Nobu Nakada

In This Thread