[#7271] Re: [PATCH] solaris 10 isinf and ruby_setenv fixes — ville.mattila@...
[#7272] [PATCH] OS X core dumps when $0 is changed and then loads shared libraries — noreply@...
Bugs item #3399, was opened at 2006-01-31 22:25
[#7274] Re: [PATCH] solaris 10 isinf and ruby_setenv fixes — ville.mattila@...
[#7277] Re: [PATCH] solaris 10 isinf and ruby_setenv fixes — ville.mattila@...
[#7280] Re: [PATCH] solaris 10 isinf and ruby_setenv fixes — ville.mattila@...
[#7286] Re: ruby-dev summary 28206-28273 — ara.t.howard@...
On Thu, 2 Feb 2006, Minero Aoki wrote:
mathew wrote:
mathew wrote:
I'm not sure we even need the 'with' syntax. Even if we do, it breaks
On 2006.02.07 10:03, Evan Webb wrote:
Umm, on what version are you seeing a warning there? I don't and never
On 2006.02.07 14:47, Evan Webb wrote:
I'd by far prefer it never emit a warning. The warning is assumes you
On Tue, 7 Feb 2006, Evan Webb wrote:
On Wed, 8 Feb 2006, Timothy J. Wood wrote:
[#7305] Re: Problem with weak references on OS X 10.3 — Mauricio Fernandez <mfp@...>
On Sun, Feb 05, 2006 at 08:33:40PM +0900, Christian Neukirchen wrote:
On Feb 5, 2006, at 5:05 AM, Mauricio Fernandez wrote:
On Wed, Feb 22, 2006 at 02:21:24PM +0900, Eric Hodel wrote:
Hi,
On Mon, Feb 27, 2006 at 12:45:28AM +0900, Yukihiro Matsumoto wrote:
On Sun, Feb 26, 2006 at 06:06:17PM +0100, Mauricio Fernandez wrote:
In article <20060226171117.GB29508@tux-chan>,
In article <[email protected]>,
Hi,
In article <m1FDshr-0006MNC@Knoppix>,
In article <[email protected]>,
In article <[email protected]>,
Just my quick 2 cents...
In article <[email protected]>,
Hi,
In article <m1FESAD-0001blC@Knoppix>,
Hi,
[#7331] Set containing duplicates — noreply@...
Bugs item #3506, was opened at 2006-02-08 22:52
[#7337] Parse error within Regexp — Bertram Scharpf <lists@...>
Hi,
Hi,
On Sun, Feb 12, 2006 at 01:34:55AM +0900, Yukihiro Matsumoto wrote:
[#7344] Ruby 1.8.4 on Mac OS X 10.4 Intel — Dae San Hwang <daesan@...>
Hi, all. This is my first time posting to this mailing list.
On Feb 12, 2006, at 6:14 AM, Dae San Hwang wrote:
[#7347] Latest change to eval.c — Kent Sibilev <ksruby@...>
It seems that the latest change to eval.c (1.616.2.154) has broken irb.
Hi,
Thanks, Matz.
[#7364] Method object used as Object#instance_eval block doesn't work (as expected) — noreply@...
Bugs item #3565, was opened at 2006-02-15 02:32
Hi,
Hi,
On Pr 2006-02-16 at 03:18 +0900, Yukihiro Matsumoto wrote:
[#7376] Minor tracer.rb patch — Daniel Berger <Daniel.Berger@...>
Hi,
[#7396] IO#reopen — Mathieu Bouchard <matju@...>
[#7403] Module#define_method "send hack" fails with Ruby 1.9 — Emiel van de Laar <emiel@...>
Hi List,
Emiel van de Laar <[email protected]> writes:
Hi --
[#7439] FYI: ruby-lang.org is on spamcop blacklists — mathew <meta@...>
dnsbl/bl.spamcop.net returned deny: for
[#7442] GC Question — zdennis <zdennis@...>
I have been posting to the ruby-talk mailing list about ruby memory and GC, and I think it's ready
Hello.
Hello.
Re: Question about massive API changes
On Jan 31, 2006, at 9:06 PM, Sean E. Russell wrote: > On Tuesday 31 January 2006 14:44, mathew wrote: >>> What do you mean by an API facade? >> >> Something that accepts calls via the old API, and translates them >> into >> appropriate calls into the new API. > > I thought that's what you meant. Unfortunately, that's not the API > I'm > talking about. > > In REXML, currently, you can do this: > > el.attributes['someatt'] = "foo" > el.attributes['someatt'] << "bar" > el.attributes['someatt'] == "foobar" # true > > I can do this, because the attributes are being stored as Attribute > objects, > even though you get back String objects from attributes[]. To get > the space > saving, I'm only generating Attribute objects when the user makes > an API call > that returns an Attribute object; otherwise, I store the original > String > objects, which are less than 1/3 the size of an Attribute object. What about using lazy evaluation for the old style methods? The documentation can warn that they are no longer the way, possibly even depreciated, and that memory usage increases dramatically with their usage. Then *if* one of them is called, the needed structures spring into existence and the old API is functional. > Depending on the XML document, this can save a significant amount > of memory. Have you played around at all with storing just offsets into the document? I have no idea if this is remotely practical. It's just a random thought I had. A tag could be four Fixnums perhaps: an open tag start offset, an open tag close offset, a close tag start offset, and a close tag stop offset. How much time does it take to parse one tag knowing all those offsets? The worry is that usage could force you to parse the same tag repeatedly, I guess, but you could potentially get away with never parsing some tags. You could cache the Strings after you parse, for later usage. You might even be able to reasonably leave the document on disk this way (using file seeking). Again, not trying to tell you how to write your library here. Just thinking out loud... James Edward Gray II