[#5524] Division weirdness in 1.9 — "Florian Frank" <flori@...>
Hi,
[#5536] bug in variable assignment — Mauricio Fern疣dez <mfp@...>
Hi,
On Mon, Aug 08, 2005 at 11:36:22AM +0900, nobuyoshi nakada wrote:
hi,
Hi,
[#5552] Exceptions in threads all get converted to a TypeError — Paul van Tilburg <paul@...>
Hey all,
[#5563] Non-overridable and non-redefinable methods — Eric Mahurin <eric_mahurin@...>
Lately, I've been thinking about the future of ruby
On 8/19/05, Eric Mahurin <eric_mahurin@yahoo.com> wrote:
--- Austin Ziegler <halostatue@gmail.com> wrote:
Just wanted to add a few things.
On 8/19/05, TRANS <transfire@gmail.com> wrote:
Hi --
--- "David A. Black" <dblack@wobblini.net> wrote:
On 8/20/05, Eric Mahurin <eric_mahurin@yahoo.com> wrote:
On 8/20/05, TRANS <transfire@gmail.com> wrote:
On 8/19/05, Eric Mahurin <eric_mahurin@yahoo.com> wrote:
--- Austin Ziegler <halostatue@gmail.com> wrote:
On 20 Aug 2005, at 02:05, Eric Mahurin wrote:
Eric Hodel wrote:
Eric Mahurin wrote:
Hi,
--- SASADA Koichi <ko1@atdot.net> wrote:
Hi,
--- SASADA Koichi <ko1@atdot.net> wrote:
[#5609] Pathname#walk for traversing path nodes (patch) — ES <ruby-ml@...>
Here is a small addition to Pathname against 1.9, probably suited
Evan Webb wrote:
In article <43094510.6090406@magical-cat.org>,
[#5651] File.extname edge case bug? — Daniel Berger <Daniel.Berger@...>
Hi all,
[#5662] Postgrey — Shugo Maeda <shugo@...>
Hi,
[#5676] uri test failures. (Re: [ruby-cvs] ruby/lib, ruby/lib/uri: Lovely RDOC patches from mathew (metaATpoboxDOTcom) on URI/* and getoptlong.rb) — Tanaka Akira <akr@...17n.org>
In article <20050824050801.5B4E0C671F@lithium.ruby-lang.org>,
[#5680] Problem with mkmf and spaces in directory names? — noreply@...
Bugs item #2308, was opened at 2005-08-25 13:42
[#5685] Wilderness Project — "Charles E. Thornton" <ruby-core@...>
OK - I see where ELTS_SHARED is used to implement COPY-ON-WRITE
Wandering in the Wilderness Project
I recently became fascinated with Ruby. I am starting a personal
project to learn ruby from the inside out. I think it is the only way to
fully understand a language that is this subtle! Toward the end, as I
read the documentation (ie THE SOURCE CODE!) I run into things that seem
to have more aspects to them than is apparent, or I just don't
understand the reason why they exist.
The questions I will be asking fall into three (for now) categories
1) WHY something was done this way
2) WHAT am I missing?
3) DO I have it right?
I intend to compile the answers to these questions into a FAQ at some
point. Any help given would be appreciated.
==========================================================================================
R U B Y - C O R E Q U E S T I O N S
==========================================================================================
0) Memory is always allocated in Quad Byte!
(Seems the basis of VALUE Interpretation)
1) VALUE Interpretation - Is the following Correct?
a) If the LSB = 1, it is a Small Integer.
b) If the VALUE is equal to 0,2,4, or 6 it is a special
constant: false, true, nil, or undef.
c) If the lower 8 bits are equal to'0xe', it is a Symbol.
d) Otherwise, it is an Object Reference
2) 'special_generic_ivar' - Is this to trigger Garbage Collection ONLY
only for Special Constant Values?
- If it is - Is it because there is no real
object in Object Space to trigger GC?
3) Question - Why not put 'iv_tbl' pointers in all Built-in Objects.
a) Can every Object have valid Instance Variables?
b) Ruby Hacking Guide seems to put forth the argument that 'iv_tbl'
entries in other Built-in Objects would waste to much memory.
aa) Why? -Four bytes per object does not seem to be a major hit?
bb) Even if it is - Memory Usage should not be a problem for the
scale of programs using Ruby - Or am I wrong?
cc) Memory is cheap and getting cheaper all time - Even at home
512K is under $45.00(US).
dd) I would trade reasonable increases in memory usage for
greater processing efficiency EVERY TIME!
--
GodFather -- 667 Neighbor of the Beast