[#6363] Re: rescue clause affecting IO loop behavior — ts <decoux@...>

>>>>> "D" == David Alan Black <dblack@candle.superlink.net> writes:

17 messages 2000/11/14
[#6367] Re: rescue clause affecting IO loop behavior — David Alan Black <dblack@...> 2000/11/14

Hello again --

[#6582] best way to interleaf arrays? — David Alan Black <dblack@...>

Hello --

15 messages 2000/11/26

[#6646] RE: Array Intersect (&) question — Aleksi Niemel<aleksi.niemela@...>

Ross asked something about widely known and largely ignored language (on

23 messages 2000/11/29
[#6652] RE: Array Intersect (&) question — rpmohn@... (Ross Mohn) 2000/11/29

aleksi.niemela@cinnober.com (Aleksi Niemel) wrote in

[#6723] Re: Array Intersect (&) question — Mathieu Bouchard <matju@...> 2000/12/01

> >Use a hash. Here's code to do both and more. It assumes that

[#6656] printing/accessing arrays and hashes — raja@... (Raja S.)

I'm coming to Ruby with a Python & Common Lisp background.

24 messages 2000/11/30

[ruby-talk:6064] xmalloc(), xfree()

From: Mathieu Bouchard <matju@...>
Date: 2000-11-05 05:21:47 UTC
List: ruby-talk #6064
I'm currently trying to make changes to xmalloc/xrealloc/xfree. The
problem is, lots of code calls free() directly instead of xfree(). I am
wondering whether there is any reason that parts of ruby (or extensions to
ruby) might want to keep using free() instead of xfree() ?

I would like that xfree() be used only on memory allocated with xmalloc(),
and free() only on memory allocated with malloc(). That would help me
alot.

matju


In This Thread

Prev Next