[#19731] use of require thread safety — "Roger Pack" <rogerpack2005@...>

I'm sure this has been discussed before, but...should there be

56 messages 2008/11/08
[#19796] Re: use of require thread safety — Nobuyoshi Nakada <nobu@...> 2008/11/11

Hi,

[#21651] Re: use of require thread safety — Charles Oliver Nutter <charles.nutter@...> 2009/01/29

Nobuyoshi Nakada wrote:

[#19798] Re: use of require thread safety — "Roger Pack" <rogerpack2005@...> 2008/11/11

> While a thread is requiring a given file, another thread which

[#20732] Re: use of require thread safety — "Roger Pack" <rogerpack2005@...> 2008/12/20

> Currently with 1.8.7 (for me) the secondmost thread continues

[#20737] Re: use of require thread safety — Charles Oliver Nutter <charles.nutter@...> 2008/12/20

Roger Pack wrote:

[#20769] Re: use of require thread safety — Charles Oliver Nutter <charles.nutter@...> 2008/12/21

Charles Oliver Nutter wrote:

[#20795] Re: use of require thread safety — Paul Brannan <pbrannan@...> 2008/12/22

On Mon, Dec 22, 2008 at 03:05:07AM +0900, Charles Oliver Nutter wrote:

[#19821] Re: use of require thread safety — Paul Brannan <pbrannan@...> 2008/11/11

On Tue, Nov 11, 2008 at 10:51:45AM +0900, Nobuyoshi Nakada wrote:

[#19829] Re: use of require thread safety — Charles Oliver Nutter <charles.nutter@...> 2008/11/11

Paul Brannan wrote:

[#19759] Proposal: Method#get_args — "Yehuda Katz" <wycats@...>

I'd like to propose a way to introspect into the arguments of a method

97 messages 2008/11/09
[#19787] Re: Proposal: Method#get_args — "Roger Pack" <rogerpack2005@...> 2008/11/11

The only question I have is why would one want to know the names of

[#19789] Re: Proposal: Method#get_args — Trans <transfire@...> 2008/11/11

On Nov 10, 7:18=A0pm, "Roger Pack" <rogerpack2...@gmail.com> wrote:

[#19818] Re: Proposal: Method#get_args — Mikael Hlund <mikael@...> 2008/11/11

Allow me to throw in my ~.116892074 DKK;

[#19837] Re: Proposal: Method#get_args — Charles Oliver Nutter <charles.nutter@...> 2008/11/11

Mikael H淡ilund wrote:

[#19838] Re: Proposal: Method#get_args — Dave Thomas <dave@...> 2008/11/11

[#19870] Re: Proposal: Method#get_args — Brian Candler <B.Candler@...> 2008/11/12

On Wed, Nov 12, 2008 at 04:48:03AM +0900, Dave Thomas wrote:

[#19874] Re: Proposal: Method#get_args — Paul Brannan <pbrannan@...> 2008/11/12

On Wed, Nov 12, 2008 at 06:01:40PM +0900, Brian Candler wrote:

[#19881] Re: Proposal: Method#get_args — Charles Oliver Nutter <charles.nutter@...> 2008/11/12

Paul Brannan wrote:

[#19887] Re: Proposal: Method#get_args — Paul Brannan <pbrannan@...> 2008/11/12

On Thu, Nov 13, 2008 at 02:06:15AM +0900, Charles Oliver Nutter wrote:

[#19889] Re: Proposal: Method#get_args — Charles Oliver Nutter <charles.nutter@...> 2008/11/12

Paul Brannan wrote:

[#19892] Re: Proposal: Method#get_args — Jim Weirich <jim.weirich@...> 2008/11/12

[#19893] Re: Proposal: Method#get_args — Jim Deville <jdeville@...> 2008/11/12

> -----Original Message-----

[#19894] Re: Proposal: Method#get_args — Brian Candler <B.Candler@...> 2008/11/12

On Thu, Nov 13, 2008 at 04:33:07AM +0900, Jim Deville wrote:

[#19895] Re: Proposal: Method#get_args — Jim Weirich <jim.weirich@...> 2008/11/12

[#19896] Re: Proposal: Method#get_args — Charles Oliver Nutter <charles.nutter@...> 2008/11/12

Jim Weirich wrote:

[#19899] Re: Proposal: Method#get_args — Jim Weirich <jim.weirich@...> 2008/11/12

On Nov 12, 2008, at 4:12 PM, Charles Oliver Nutter wrote:

[#19915] Re: Proposal: Method#get_args — Brian Candler <B.Candler@...> 2008/11/13

On Thu, Nov 13, 2008 at 07:02:25AM +0900, Jim Weirich wrote:

[#19927] Re: {Proc,Method}#parameters (Re: Proposal: Method#get_args) — Nobuyoshi Nakada <nobu@...> 2008/11/14

Hi,

[#19784] Status of copy-on-write friendly garbage collector — Hongli Lai <hongli@...99.net>

Hi.

22 messages 2008/11/10
[#19799] Re: Status of copy-on-write friendly garbage collector — "Narihiro Nakamura" <authornari@...> 2008/11/11

Hi.

[#19812] Re: Status of copy-on-write friendly garbage collector — "Yehuda Katz" <wycats@...> 2008/11/11

Narihiro,

[#19823] Re: Status of copy-on-write friendly garbage collector — Yukihiro Matsumoto <matz@...> 2008/11/11

Hi,

[#19845] [Bug #743] Socket.gethostbyname returns odd values — Roger Pack <redmine@...>

Bug #743: Socket.gethostbyname returns odd values

11 messages 2008/11/11

[#19846] [Bug #744] memory leak in callcc? — Roger Pack <redmine@...>

Bug #744: memory leak in callcc?

142 messages 2008/11/11
[#21394] [Bug #744] memory leak in callcc? — Roger Pack <redmine@...> 2009/01/17

Issue #744 has been updated by Roger Pack.

[#21429] Re: [Bug #744] memory leak in callcc? — Brent Roman <brent@...> 2009/01/19

[#21441] Re: [Bug #744] memory leak in callcc? — Nobuyoshi Nakada <nobu@...> 2009/01/19

Hi,

[#21483] Re: [Bug #744] memory leak in callcc? — Brent Roman <brent@...> 2009/01/21

[#21487] Re: [Bug #744] memory leak in callcc? — Michal Babej <calcifer@...> 2009/01/21

On Wednesday 21 of January 2009 10:21:19 Brent Roman wrote:

[#21711] Re: [Bug #744] memory leak in callcc? — Brent Roman <brent@...> 2009/02/01

[#22062] Re: [Bug #744] memory leak in callcc? — Roger Pack <rogerdpack@...> 2009/02/14

>> I've tried that myself but it didn't work very well

[#22265] Re: [Bug #744] memory leak in callcc? — Michal Babej <calcifer@...> 2009/02/19

On Saturday 14 of February 2009 08:17:22 Roger Pack wrote:

[#21514] Re: [Bug #744] memory leak in callcc? — Brent Roman <brent@...> 2009/01/22

[#19945] [Bug #744] memory leak in callcc? — Roger Pack <redmine@...> 2008/11/15

Issue #744 has been updated by Roger Pack.

[#19968] Re: [Bug #744] memory leak in callcc? — Brent Roman <brent@...> 2008/11/17

[#19969] Re: [Bug #744] memory leak in callcc? — Martin Duerst <duerst@...> 2008/11/17

At 12:54 08/11/17, Brent Roman wrote:

[#19970] Re: [Bug #744] memory leak in callcc? — Brent Roman <brent@...> 2008/11/17

[#19972] Re: [Bug #744] memory leak in callcc? — Kurt Stephens <kurt@...> 2008/11/17

A common technique is to allocate a reasonably sized array (256-bytes)

[#20149] Promising C coding techniques to reduce MRI's memory use — Brent Roman <brent@...> 2008/11/28

[#20517] Re: Promising C coding techniques to reduce MRI's memory use — "Roger Pack" <rogerpack2005@...> 2008/12/13

> I implemented a scheme for recording the maximum depth of the C stack in

[#20534] Re: Promising C coding techniques to reduce MRI's memory use — Brent Roman <brent@...> 2008/12/13

[#20750] [PATCH] Promising C coding techniques to reduce MRI's memory use — Brent Roman <brent@...> 2008/12/21

[#20751] Re: [PATCH] Promising C coding techniques to reduce MRI's memory use — Ezra Zygmuntowicz <ezmobius@...> 2008/12/21

[#20752] Re: [PATCH] Promising C coding techniques to reduce MRI's memory use — Brent Roman <brent@...> 2008/12/21

[#20781] Re: [PATCH] Promising C coding techniques to reduce MRI's memory use — "Roger Pack" <rogerpack2005@...> 2008/12/22

First thanks for doing all that hard work. I'm sure it's not pleasant

[#20783] Re: [PATCH] Promising C coding techniques to reduce MRI's memory use — Brent Roman <brent@...> 2008/12/22

[#20903] Re: [PATCH] Promising C coding techniques to reduce MRI's memory use — "Roger Pack" <rogerpack2005@...> 2008/12/26

Seems to overall be a tidge slower for "micro" stuff--5 or 10%.

[#20914] Re: [PATCH] Promising C coding techniques to reduce MRI's memory use — Brent Roman <brent@...> 2008/12/27

[#20922] Re: [PATCH] Promising C coding techniques to reduce MRI's memory use — "Roger Pack" <rogerpack2005@...> 2008/12/27

> You ran this benchmark suite, correct?

[#20931] Re: [PATCH] Promising C coding techniques to reduce MRI's memory use — Brent Roman <brent@...> 2008/12/28

[#20995] Re: [PATCH] Promising C coding techniques to reduce MRI's memory use — "Roger Pack" <rogerpack2005@...> 2008/12/30

Hmm interesting.

[#21261] Re: [PATCH] Promising C coding techniques to reduce MRI's memory use — "Stephen Sykes" <sdsykes@...> 2009/01/11

Brent,

[#20168] Re: Promising C coding techniques to reduce MRI's memory use — Nobuyoshi Nakada <nobu@...> 2008/11/30

Hi,

[#20175] Re: Promising C coding techniques to reduce MRI's memory use — Brian Candler <B.Candler@...> 2008/11/30

The problem can be demonstrated with a very simple program (attached), and

[#20178] Re: Promising C coding techniques to reduce MRI's memory use — Brent Roman <brent@...> 2008/11/30

[#20185] Re: Promising C coding techniques to reduce MRI's memory use — Brian Candler <B.Candler@...> 2008/12/01

> What I did come up with was not ugly at all. Factor the unwieldy switch

[#19938] Fibers in 1.8 — "Aman Gupta" <rubytalk@...1.net>

Are there any plans to backport Fiber to ruby 1.8?

13 messages 2008/11/15

[#20008] [Bug #766] 'Not enough space' error on windows — Ittay Dror <redmine@...>

Bug #766: 'Not enough space' error on windows

17 messages 2008/11/20

[#20092] [Bug #797] bug or feature: local method ? — Francois Proulx <redmine@...>

Bug #797: bug or feature: local method ?

23 messages 2008/11/25
[#20097] Re: [Bug #797] bug or feature: local method ? — Yukihiro Matsumoto <matz@...> 2008/11/25

Hi,

[#20098] Re: [Bug #797] bug or feature: local method ? — Dave Thomas <dave@...> 2008/11/25

[#20100] Re: [Bug #797] bug or feature: local method ? — Yukihiro Matsumoto <matz@...> 2008/11/25

Hi,

[#20127] Re: [Bug #797] bug or feature: local method ? — Francoys <francois.pr@...> 2008/11/26

Yukihiro Matsumoto wrote:

[ruby-core:19926] Re: flay is so awesome!

From: Ryan Davis <ryand-ruby@...>
Date: 2008-11-14 02:45:12 UTC
List: ruby-core #19926
On Nov 13, 2008, at 13:29 , Spencer Rinehart wrote:

>
> On Fri, 2008-11-14 at 06:03 +0900, Pit Capitain wrote:
>> Really impressive, Ryan! Do you know of similar tools for Java?
>
> There is Simian - http://www.redhillconsulting.com.au/products/ 
> simian/ -
> it actually works a bit better than flay at the moment - although flay
> has promise for working better with ruby code.

Umm... Actually... flay kicks simian's ass. :P

Simian, as well as a similar java tool I've used called same, have  
completely different objectives than flay. AFAIK, they're only  
normalizing whitespace and stripping comments and looking for  
duplicate code. I'm sure of that for same as I studied it for porting.  
But, I'm not positive about simian.

Simian would NEVER point this out:

> Matches found in :defn (mass = 32)
>   A: ../../drawr/dev/lib/drawr.rb:38
>   B: ../../png/dev/lib/png.rb:181
>
> A: def write(file)
> B: def save(path)
> A:   File.open(file, "wb") { |f| f.write(to_s) }
> B:   File.open(path, "wb") { |f| f.write(to_blob) }
>    end

especially considering the code is actually written like this:

>     def write(file); File.open(file, 'wb') { |f| f.write to_s }; end

vs

>   def save(path)
>     File.open path, 'wb' do |f|
>       f.write to_blob
>     end
>   end


Notice that there are 11 duplicates found by simian. Notice that there  
are 11 matches listed by flay as identicial... but then also notice  
that flay 10 more similarities that are also candidates for  
refactoring. That is where flay really differentiates itself from the  
rest. It is NOT just looking at text. It is looking at the structure  
of your code.

> % java -jar bin/simian-2.2.24.jar -language=ruby unit/itemconfig.rb
> Similarity Analyser 2.2.24 - http://www.redhillconsulting.com.au/products/simian/index.html
> Copyright (c) 2003-08 RedHill Consulting Pty. Ltd.  All rights  
> reserved.
> Simian is not free unless used solely for non-commercial or  
> evaluation purposes.
> {failOnDuplication=true, ignoreCharacterCase=true,  
> ignoreCurlyBraces=true, ignoreIdentifierCase=true,  
> ignoreModifiers=true, ignoreStringCase=true, language=Ruby,  
> threshold=6}
> Found 6 duplicate lines in the following files:
>  Between lines 464 and 472 in unit/itemconfig.rb
>  Between lines 304 and 310 in unit/itemconfig.rb
> Found 6 duplicate lines in the following files:
>  Between lines 623 and 630 in unit/itemconfig.rb
>  Between lines 463 and 470 in unit/itemconfig.rb
> Found 7 duplicate lines in the following files:
>  Between lines 294 and 301 in unit/itemconfig.rb
>  Between lines 652 and 660 in unit/itemconfig.rb
> Found 8 duplicate lines in the following files:
>  Between lines 827 and 837 in unit/itemconfig.rb
>  Between lines 664 and 673 in unit/itemconfig.rb
> Found 8 duplicate lines in the following files:
>  Between lines 529 and 539 in unit/itemconfig.rb
>  Between lines 369 and 379 in unit/itemconfig.rb
>  Between lines 895 and 905 in unit/itemconfig.rb
> Found 10 duplicate lines in the following files:
>  Between lines 842 and 852 in unit/itemconfig.rb
>  Between lines 476 and 486 in unit/itemconfig.rb
> Found 16 duplicate lines in the following files:
>  Between lines 680 and 702 in unit/itemconfig.rb
>  Between lines 850 and 872 in unit/itemconfig.rb
> Found 18 duplicate lines in the following files:
>  Between lines 706 and 734 in unit/itemconfig.rb
>  Between lines 343 and 371 in unit/itemconfig.rb
> Found 19 duplicate lines in the following files:
>  Between lines 310 and 332 in unit/itemconfig.rb
>  Between lines 673 and 695 in unit/itemconfig.rb
> Found 58 duplicate lines in the following files:
>  Between lines 737 and 826 in unit/itemconfig.rb
>  Between lines 374 and 463 in unit/itemconfig.rb
> Found 93 duplicate lines in the following files:
>  Between lines 855 and 989 in unit/itemconfig.rb
>  Between lines 489 and 623 in unit/itemconfig.rb
> Found 490 duplicate lines in 21 blocks in 1 files
> Processed a total of 692 significant (1062 raw) lines in 1 files
> Processing time: 0.302sec

vs:

> % ruby -Ilib bin/flay unit/itemconfig.rb
> Processing unit/itemconfig.rb
>
> IDENTICAL Matches found in :block (mass*2 = 640)
>   unit/itemconfig.rb:603
>   unit/itemconfig.rb:969
>
> IDENTICAL Matches found in :if (mass*3 = 621)
>   unit/itemconfig.rb:308
>   unit/itemconfig.rb:465
>   unit/itemconfig.rb:625
>
> IDENTICAL Matches found in :when (mass*2 = 612)
>   unit/itemconfig.rb:435
>   unit/itemconfig.rb:798
>
> Matches found in :when (mass = 572)
>   unit/itemconfig.rb:343
>   unit/itemconfig.rb:379
>   unit/itemconfig.rb:706
>   unit/itemconfig.rb:742
>
> IDENTICAL Matches found in :when (mass*2 = 564)
>   unit/itemconfig.rb:415
>   unit/itemconfig.rb:778
>
> IDENTICAL Matches found in :when (mass*2 = 540)
>   unit/itemconfig.rb:582
>   unit/itemconfig.rb:948
>
> Matches found in :when (mass = 500)
>   unit/itemconfig.rb:509
>   unit/itemconfig.rb:539
>   unit/itemconfig.rb:875
>   unit/itemconfig.rb:905
>
> IDENTICAL Matches found in :when (mass*2 = 492)
>   unit/itemconfig.rb:569
>   unit/itemconfig.rb:935
>
> Matches found in :when (mass = 452)
>   unit/itemconfig.rb:365
>   unit/itemconfig.rb:401
>   unit/itemconfig.rb:728
>   unit/itemconfig.rb:764
>
> IDENTICAL Matches found in :or (mass*4 = 416)
>   unit/itemconfig.rb:308
>   unit/itemconfig.rb:672
>   unit/itemconfig.rb:1038
>   unit/itemconfig.rb:1049
>
> Matches found in :when (mass = 404)
>   unit/itemconfig.rb:314
>   unit/itemconfig.rb:677
>
> Matches found in :when (mass = 380)
>   unit/itemconfig.rb:528
>   unit/itemconfig.rb:558
>   unit/itemconfig.rb:894
>   unit/itemconfig.rb:924
>
> IDENTICAL Matches found in :if (mass*2 = 336)
>   unit/itemconfig.rb:672
>   unit/itemconfig.rb:827
>
> IDENTICAL Matches found in :when (mass*2 = 124)
>   unit/itemconfig.rb:431
>   unit/itemconfig.rb:794
>
> Matches found in :when (mass = 84)
>   unit/itemconfig.rb:182
>   unit/itemconfig.rb:192
>   unit/itemconfig.rb:207
>
> IDENTICAL Matches found in :lasgn (mass*2 = 76)
>   unit/itemconfig.rb:458
>   unit/itemconfig.rb:821
>
> Matches found in :attrasgn (mass = 68)
>   unit/itemconfig.rb:302
>   unit/itemconfig.rb:638
>   unit/itemconfig.rb:661
>   unit/itemconfig.rb:1009
>
> IDENTICAL Matches found in :and (mass*2 = 68)
>   unit/itemconfig.rb:649
>   unit/itemconfig.rb:1020
>
> Matches found in :when (mass = 64)
>   unit/itemconfig.rb:175
>   unit/itemconfig.rb:185
>
> Matches found in :call (mass = 32)
>   unit/itemconfig.rb:213
>   unit/itemconfig.rb:224
>
> Matches found in :if (mass = 32)
>   unit/itemconfig.rb:156
>   unit/itemconfig.rb:264

In This Thread