ruby-talk

Mailing Lists

ruby-list (For Ruby users, JA) ruby-dev (For Ruby developers, JA) ruby-core (For Ruby developers, EN) ruby-talk (For Ruby users, EN)

[#264] Ruby 1.3.2-990402 — Yukihiro Matsumoto <matz@...>

Ruby 1.3.2-990402 is out, check out:

1 message 1999/04/02

[#266] Ruby 1.3.2-990405 — Yukihiro Matsumoto <matz@...>

Ruby 1.3.2-990405 is out, check out:

1 message 1999/04/05

[#267] Ruby 1.3.2-990408 — Yukihiro Matsumoto <matz@...>

Ruby 1.3.2-990408 is out, check out:

1 message 1999/04/08

[#268] win32 request — "bryce" <thecrow@...>

Matz, would it be possible for you to not only have the

2 messages 1999/04/11

[#269] Re: win32 request — gotoken@... (GOTO Kentaro) 1999/04/12

Hi,

[#270] a bit off topic — "bryce" <thecrow@...>

I was wondering why Ruby doesn't have a newsgroup?

2 messages 1999/04/12

[#271] Re: a bit off topic — matz@... (Yukihiro Matsumoto) 1999/04/13

Hi.

[#272] ruby 1.2.5 is released — matz@... (Yukihiro Matsumoto)

Hi.

1 message 1999/04/13

[#273] Ruby 1.3.2-990413 — Yukihiro Matsumoto <matz@...>

Ruby 1.3.2-990413 is out, check out:

1 message 1999/04/13

[#274] IPv6-ready ruby — Jun-ichiro itojun Hagino <itojun@...>

We KAME team (www.kame.net) are working on IPv6-ready ruby.

7 messages 1999/04/13

[#275] Re: IPv6-ready ruby — gotoken@... (GOTO Kentaro) 1999/04/14

In message "[ruby-talk:00274] IPv6-ready ruby"

[#276] Re: IPv6-ready ruby — Jun-ichiro itojun Hagino <itojun@...> 1999/04/14

[#277] Re: IPv6-ready ruby — gotoken@... (GOTO Kentaro) 1999/04/14

In message "[ruby-talk:00276] Re: IPv6-ready ruby"

[#278] Re: IPv6-ready ruby — Jun-ichiro itojun Hagino <itojun@...> 1999/04/14

>> Snapshot dated 19990413 may not work on IPv4-only environment.

[#279] Re: IPv6-ready ruby — gotoken@... (GOTO Kentaro) 1999/04/14

In message "[ruby-talk:00278] Re: IPv6-ready ruby"

[#280] Re: IPv6-ready ruby — Jun-ichiro itojun Hagino <itojun@...> 1999/04/14

[#281] 'case' question — "bryce" <thecrow@...>

The following code works fine:

2 messages 1999/04/14

[#282] Re: 'case' question — matz@... (Yukihiro Matsumoto) 1999/04/15

Hi.

[#283] Object delete itself? — "bryce" <thecrow@...>

Can an object delete itself?

2 messages 1999/04/17

[#284] Re: Object delete itself? — matz@... (Yukihiro Matsumoto) 1999/04/17

[#285] Ruby/Win32 question — "bryce" <thecrow@...>

I have a window class instance.

4 messages 1999/04/22

[#286] Re: Ruby/Win32 question — matz@... (Yukihiro Matsumoto) 1999/04/23

Hi.

[#289] Re: Ruby/Win32 question — "Bryce Dooley" <thecrow@...> 1999/04/26

> |

[#290] Re: Ruby/Win32 question — matz@... (Yukihiro Matsumoto) 1999/04/27

Hi.

[#287] Extensions to Ruby — Michael Neumann <neumann@...>

2 messages 1999/04/25

[#288] Re: Extensions to Ruby — "Bryce Dooley" <thecrow@...> 1999/04/25

> How can I write extensions to ruby?

[#291] AW: Re: Extensions to Ruby — Michael Neumann <neumann@...>

> Michael,

4 messages 1999/04/27

[#294] Re: AW: Re: Extensions to Ruby — KIMURA Koichi <kimura@...> 1999/04/28

[#292] Re: AW: Re: Extensions to Ruby — "Bryce Dooley" <thecrow@...> 1999/04/27

> But there's still one problem: I use VC++ and want to create a DLL.

[#293] Re: AW: Re: Extensions to Ruby — matz@... (Yukihiro Matsumoto) 1999/04/28

Hi.

[#295] AW: Re: AW: Re: Extensions to Ruby — Michael Neumann <neumann@...>

> Let me know how this goes for you.

2 messages 1999/04/28

[#296] Re: AW: Re: AW: Re: Extensions to Ruby — "Bryce Dooley" <thecrow@...> 1999/04/28

> Am I right that you are the one who writes a GUI for Windows?

[#297] Ruby 1.3.3-990430 — matz <matz@...>

Ruby 1.3.3-990430 is out, check out:

1 message 1999/04/30

[#298] AW: Re: AW: Re: AW: Re: Extensions to Ruby — Michael Neumann <neumann@...>

> Of course, anyone who wants to contribute to the project is very

2 messages 1999/04/30

[#299] Re: AW: Re: AW: Re: AW: Re: Extensions to Ruby — "Bryce Dooley" <thecrow@...> 1999/05/07

I apologize for the delay in my reply.

[ruby-talk:00289] Re: Ruby/Win32 question

From: "Bryce Dooley" <thecrow@...>

Date: 1999-04-26 22:27:55 UTC

List: ruby-talk #289

> |
> |I want the object to be destroyed regardless of how many
> |references there are to it when the WM_DESTROY message
> |is received by object 'x' (which is the window).
> 
> Hmm, for example, IO objects are NOT destroyed on close(), even though
> any operation on them are useless.  They raise exceptions for
> operations after closing.  I think it's enough for treating
> WM_DESTROYed Window objects as well.
> 

Matz, it sounds like this has potential to be a serious memory leak.
Would that be a correct statement?  If so, can I interact with the
garbage collector to collect these objects? or something like that...???

Thanks.
Bryce

Thread

In This Thread