[#1207] warning in ruby extension eats memory — Eugene Scripnik <Eugene.Scripnik@...>
This message was posted to ruby-talk, but I didn't get responce from
>>>>> "E" == Eugene Scripnik <Eugene.Scripnik@itgrp.net> writes:
ts wrote:
>>>>> "E" == Eugene Scripnik <Eugene.Scripnik@itgrp.net> writes:
ts wrote:
>>>>> "E" == Eugene Scripnik <Eugene.Scripnik@itgrp.net> writes:
ts wrote:
>>>>> "E" == Eugene Scripnik <Eugene.Scripnik@itgrp.net> writes:
ts wrote:
>>>>> "E" == Eugene Scripnik <Eugene.Scripnik@itgrp.net> writes:
Hi,
[#1229] stack problem — Mathieu Bouchard <matju@...>
On Sat, Jul 12, 2003 at 01:59:53PM +0900, Mathieu Bouchard wrote:
On Tue, Jul 15, 2003 at 01:26:43AM +0900, Mathieu Bouchard wrote:
Hi,
[#1237] FTP.new with block — Gavin Sinclair <gsinclair@...>
Hi,
>>>>> "G" == Gavin Sinclair <gsinclair@soyabean.com.au> writes:
Hi,
Mathieu Bouchard wrote:
On Sun, Jul 20, 2003 at 03:06:13AM +0900, Dave Thomas wrote:
>>>>> "R" == Richard Zidlicky <rz@linux-m68k.org> writes:
On Sun, Jul 20, 2003 at 06:51:03PM +0900, ts wrote:
>>>>> "R" == Richard Zidlicky <rz@linux-m68k.org> writes:
On Mon, Jul 21, 2003 at 09:59:19PM +0900, ts wrote:
[#1249] File.write(path, data)? — Gavin Sinclair <gsinclair@...>
I am glad to see File.read(path) in Ruby 1.8. But what about
[#1256] testunit, exit status and at_exit — Dave Thomas <dave@...>
I'd really like TestUnit to be able to return an exit status when I run
-----BEGIN PGP SIGNED MESSAGE-----
Sean E. Russell [mailto:ser@germane-software.com] wrote:
Hi,
[#1257] Add have_defined() and rework have_struct_member() — Michal Rokos <m.rokos@...>
Hello,
[#1297] Fix for Bug 1058 — Markus Walser <walser@...>
Hi,
Hi,
On Friday 25 July 2003 10:58, Yukihiro Matsumoto wrote:
Hi,
On Friday 25 July 2003 11:46, Yukihiro Matsumoto wrote:
I tried to figure out what's wrong. So far I havn't a solution:
Hello,
> Check the value of klass by
Hi,
[#1309] exceptions and such — Mathieu Bouchard <matju@...>
[#1310] adding NodeDump and ii — nobu.nokada@...
Hi,
>>>>> "n" == nobu nokada <nobu.nokada@softhome.net> writes:
Re: [Patch] FTP.new with block
On Sat, 19 Jul 2003, ts wrote: > >>>>> "G" == Gavin Sinclair <gsinclair@soyabean.com.au> writes: > G> FTP.new and FTP.open are like their File counterparts: they accept a > G> block, pass in the ftp object, and ensure the FTP connection is closed > G> at the end of (or premature exit from) the block. > Why all persons think that File::new can take a block ? That's psychological: when people have a lot of things to learn, they (carefully or not) forget the pieces that they can reinvent on the fly. The brain can thus achieve a quite good compression ratio on a lot of things. This is why consistency is good, as it makes things more compressible. Sometimes the forgetting may be careful and almost deliberate, and thus lossless or almost, sometimes that's more careless and lossy but with the knowledge that the memory is partial, and sometimes people have the impression of remembering something exactly while the memory has been lossy. [That may be something well-known in psychology but I don't have formal knowledge in that so I couldn't tell. Let's just call it the Matju Hypothesis (tm) for now. heh] So I think that in this particular case, it works like this: 1. people think they know the Ruby API 2. people only ever use File.open 3. people know the block option thereof and use it 4. people know there is a File.new 5. people know Ruby has an "alias" feature and that matz uses it (eg. Array#indices,#indexes; Enumerable#collect,#map) 6. people know that File.open and .new play the same role 7. people think there is no point in making File.open not like .new. 8. so people assume there is a common method, with an alias. that makes sense to anyone? ________________________________________________________________ Mathieu Bouchard http://artengine.ca/matju