[#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: One-Click Installer: MinGW? or VC2005?

From: nobu@...
Date: 2006-07-19 07:48:43 UTC
List: ruby-core #8269
Hi,

At Wed, 19 Jul 2006 14:49:28 +0900,
Charlie Savage wrote in [ruby-core:08267]:
> When I build an extension with VC++ 2005, the extension links against
> msvcr80.dll (never had compile/link issues with the Ruby headers and
> libraries).  Which means that two CRTs are now in play, msvcrt.dll and
> msvcr80.dll (which is also dependent on msvcrt.dll).  At this point you
> have to be careful about passing CRT resources between the two CRTs or
> else you'll crash the program.

And you have to count external DLLs - Iconv, SSLeay, PDcurses,
etc.

> And I'd guess this is where my experience is different - for the
> extensions I've built the communication between the extension and Ruby
> has been done only via the Ruby C API.  There haven't been any examples,
> like you mention above, where Ruby and the extension communicated via a
> CRT function such as get_errno and set_errno.

Can you let other products use Ruby API?

The possible (and perhaps the only) way would be compiling all
sources by yourself.

-- 
Nobu Nakada

In This Thread