[#7476] Net::HTTP Bug in Ruby 1.8.4? — James Edward Gray II <james@...>
Can a Net::HTTP guru comment on this message:
[#7485] Bugzilla for ruby? — Hadmut Danisch <hadmut@...>
Hi,
[#7493] how to introduce reference objects into ruby — "Geert Fannes" <Geert.Fannes@...>
Hello,
[#7497] Re: how to introduce reference objects into ruby — "Geert Fannes" <Geert.Fannes@...>
Hello,
[#7500] Re: how to introduce reference objects into ruby — "Geert Fannes" <Geert.Fannes@...>
The problem with the code you sent is that you have to go through ALL
The columns store the actual values (doubles), and the rows store pointers to the corresponding doubles. This way, I can update a double directly via the columns, via the rows after dereferencing the pointers.
[#7518] Proposal: String#notempty? — Bertram Scharpf <lists@...>
Hi,
[#7524] Sefe level: bug or feature? — "Kirill A. Shutemov" <k.shutemov@...>
Why cannot do eval with $SAFE=3 and can with $SAFE=4? Is it bug or
Hi,
On Mon, 13 Mar 2006, Yukihiro Matsumoto wrote:
[#7529] Re: Proposal: String#notempty? — "Berger, Daniel" <Daniel.Berger@...>
> -----Original Message-----
[#7546] Re: how to introduce reference objects into ruby — "Geert Fannes" <Geert.Fannes@...>
In Ruby, there's the []= and [] operators which you can define together.
[#7553] "not" operator used in expression that is a method parameter can generate syntax error — noreply@...
Bugs item #3843, was opened at 2006-03-15 22:09
Hi,
Nobu, you are not answering to the question.... You have to unveil why
Hi,
Hello,
Zev Blut wrote:
On 3/16/06, Joel VanderWerf <vjoel@path.berkeley.edu> wrote:
On 3/16/06, Zev Blut <rubyzbibd@ubit.com> wrote:
Hello,
Yukihiro Matsumoto wrote:
On 3/16/06, mathew <meta@pobox.com> wrote:
Brian Mitchell wrote:
On 3/16/06, mathew <meta@pobox.com> wrote:
Dear all
What you've described is the basic predence difference between
Evan Phoenix wrote:
[#7600] ruby_script ? — "Nicolas Despr鑚" <nicolas.despres@...>
Hi list,
>>>>> "N" == Nicolas Despr=E8s?= <ISO-8859-1> writes:
On 3/25/06, ts <decoux@moulon.inra.fr> wrote:
>>>>> "N" == Nicolas Despr=E8s?= <ISO-8859-1> writes:
[#7601] to_str, to_s and StringValue — "Gerardo Santana Gez Garrido" <gerardo.santana@...>
If I understand correctly, StringValue is a way for writing duck-type
[#7614] PATCH: A subclassable Pathname — "Evan Phoenix" <evanwebb@...>
A simply change (changing all references of "Pathname.new" to
In article <92f5f81d0603262350k796fe48fp2224b9f2108ac507@mail.gmail.com>,
Quite right on the .glob and .getwd. I guess the tests don't test hit
In article <92f5f81d0603270903g2fb02244i6a395be708dfffa3@mail.gmail.com>,
In article <87fyl3x0wd.fsf@m17n.org>,
Hm, well, thats because of the shortcut behavior in Pathname#+ which
In article <92f5f81d0603271717r1ce51d30p6c28e363dc32a09b@mail.gmail.com>,
[ ruby-Bugs-3698 ] In a highly dynamic ObjectSpace (loads of created and collected objects) YAML creates erroneous anchors/references
Bugs item #3698, was opened at 2006-03-01 19:10
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=3698&group_id=426
Category: Standard Library
Group: v1.0 (example)
Status: Open
Resolution: None
Priority: 3
Submitted By: Hannes Wyss (hwyss)
Assigned to: Nobody (None)
Summary: In a highly dynamic ObjectSpace (loads of created and collected objects) YAML creates erroneous anchors/references
Initial Comment:
Here is a script that demonstrates the problem:
#!/usr/bin/env ruby
require 'yaml'
class Foo
def collection
## simulate a cached environment where Object are loaded on demand
@collection ||= [Object.new]
end
def to_yaml(opts={})
res = YAML::quick_emit( self.object_id, opts ) { |out|
out.map( taguri ) { |map|
## create a temporary Array with relevant data - in the real-world
## case this is not a dup, but I can reproduce the problem much faster this way
map.add('collection', collection.collect { |o| o.dup })
}
}
GC.start
res
end
end
foos = []
dump = ''
until(/id/.match(dump = foos.to_yaml))
foos.push(Foo.new)
end
puts "Id-Collision in YAML after #{foos.size} attempts"
#puts dump
On a PowerBook with 1G ram:
hwyss@lapdog ~ $ ruby -v
ruby 1.8.4 (2006-02-24) [powerpc-linux]
hwyss@lapdog ~ $ ruby collision.rb
Id-Collision in YAML after 3 attempts
---
- !ruby/object:Foo
collection:
- &id001 !ruby/object {}
- !ruby/object:Foo
collection:
- !ruby/object {}
- !ruby/object:Foo
collection:
- *id001
On a i686 with 2 G ram:
ywesee@HotPower ~ $ ruby -v
ruby 1.8.4 (2006-02-24) [i686-linux]
ywesee@HotPower ~ $ ruby collision.rb
Id-Collision in YAML after 74 attempts
An attempt at working around the Problem using ObjectSpace#define_finalizer is attached. However I am not sure
a) whether this really is unexpected Behavior
b) if the suggested workaround is the best available
c) whether referencing the emitter in the finalizer-proc will prevent it from being garbage collected
TIA for your help
Hannes
----------------------------------------------------------------------
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=3698&group_id=426