ruby-core

On 2/22/06, George Ogata <g_ogata@optushome.com.au> wrote:> dblack@wobblini.net writes:>> I'm still not happy about #funcall. How is one supposed to remember>> which (#send or #funcall) is which? There are a few things in Ruby>> where "you just have to memorize it" -- like the true/false arguments>> to #instance_methods, or the differences between Proc.new and lambda.>> I've always felt that these are soft spots in the language.>> #send/#funcall seems to me to be in the same category.> #funcall breaks the rules. That makes it "fun". ;-)

[#7413] Re: Module#define_method "send hack" fails with Ruby 1.9 — "Justin Bailey" <jgbailey@...> 2006/02/22

Second! I've disliked 'funcall' since I first saw it. And why break send? I

[#7419] ping.rb — "Pat Eyler" <rubypate@...>

ping.rb has bothered me for a while for two reasons. First, it really ought

4 messages 2006/02/24

[#7425] Re: ping.rb — Joel VanderWerf <vjoel@...> 2006/02/25

Pat Eyler wrote:

[#7420] Re: ping.rb — Daniel Berger <djberg96@...> 2006/02/24

--- Pat Eyler <rubypate@gmail.com> wrote:

[#7421] Re: ping.rb — "Pat Eyler" <rubypate@...> 2006/02/24

On 2/23/06, Daniel Berger <djberg96@yahoo.com> wrote:

[#7422] Syck fails with parse error on parsing multiple documents — noreply@...

Bugs item #3654, was opened at 2006-02-24 15:45

1 message 2006/02/24

[#7423] Rubygems/ri integration — Eric Hodel <drbrain@...7.net>

I just added a patch to Rubygems that allows it to generate ri data

3 messages 2006/02/24

[#7426] Re: [PATCH] Rubygems/ri integration — Ryan Davis <ryand-ruby@...> 2006/02/26

[#7479] Re: [PATCH] Rubygems/ri integration — Yukihiro Matsumoto <matz@...> 2006/03/03

Hi,

[#7424] Passing wrong data type to Win32API#call causes segfault — noreply@...

Bugs item #3658, was opened at 2006-02-24 19:33

1 message 2006/02/25

[#7434] parser bug, function call without parens across multiple lines — David Smiley <dsmiley@...>

I have encountered a counter-intuitive bug in Ruby's parser. The

5 messages 2006/02/27

[#7436] Re: parser bug, function call without parens across multiple lines — Mauricio Fernandez <mfp@...> 2006/02/27

On Tue, Feb 28, 2006 at 02:05:17AM +0900, David Smiley wrote:

[#7441] Re: parser bug, function call without parens across multiple lines — David Smiley <dsmiley@...> 2006/02/27

First of all, I'd like to apologize because my bug report was

[#7435] Re: parser bug, function call without parens across multiple lines — ts <decoux@...> 2006/02/27

>>>>> "D" == David Smiley <dsmiley@mitre.org> writes:

[#7437] Re: parser bug, function call without parens across multiple lines — Stefan Lang <langstefan@...> 2006/02/27

On Monday 27 February 2006 18:05, David Smiley wrote:

[#7438] Re: parser bug, function call without parens across multiple lines — "Yemi D. Bedu" <yemi@...>

Hello,

1 message 2006/02/27

[#7439] FYI: ruby-lang.org is on spamcop blacklists — mathew <meta@...>

dnsbl/bl.spamcop.net returned deny: for

3 messages 2006/02/27

[#7440] Re: FYI: ruby-lang.org is on spamcop blacklists — "Justin Bailey" <jgbailey@...> 2006/02/27

This is fairly serious as it breaks Google Groups/Ruby Talk list

[#7464] Re: FYI: ruby-lang.org is on spamcop blacklists — "Austin Ziegler" <halostatue@...> 2006/03/01

On 2/27/06, Justin Bailey <jgbailey@gmail.com> wrote:> This is fairly serious as it breaks Google Groups/Ruby Talk list> integration, right?

[#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

17 messages 2006/02/27

[#7446] Re: GC Question — "H.Yamamoto" <ocean@...2.ccsnet.ne.jp> 2006/02/28

Hello.

[#7449] Re: GC Question — "H.Yamamoto" <ocean@...2.ccsnet.ne.jp> 2006/02/28

Hello.

[#7450] Re: GC Question — "H.Yamamoto" <ocean@...2.ccsnet.ne.jp> 2006/02/28

Sorry, I lied...

[#7451] Re: GC Question — ts <decoux@...> 2006/02/28

>>>>> "H" == H Yamamoto <ocean@m2.ccsnet.ne.jp> writes:

[#7452] Re: GC Question — "H.Yamamoto" <ocean@...2.ccsnet.ne.jp> 2006/02/28

[#7453] Re: GC Question — ts <decoux@...> 2006/02/28

>>>>> "H" == H Yamamoto <ocean@m2.ccsnet.ne.jp> writes:

[#7454] Re: GC Question — "H.Yamamoto" <ocean@...2.ccsnet.ne.jp> 2006/02/28

[#7455] Re: GC Question — ts <decoux@...> 2006/02/28

>>>>> "H" == H Yamamoto <ocean@m2.ccsnet.ne.jp> writes:

[#7462] Re: GC Question — zdennis <zdennis@...> 2006/02/28

H.Yamamoto wrote:

[#7456] Re: GC Question — zdennis <zdennis@...> 2006/02/28

Attempting to apply patch to array.c from 1.8.4 I get:

[#7458] Re: GC Question — ts <decoux@...> 2006/02/28

>>>>> "z" == zdennis <zdennis@mktec.com> writes:

[#7459] Re: GC Question — zdennis <zdennis@...> 2006/02/28

ts wrote:

[#7461] Re: GC Question — ts <decoux@...> 2006/02/28

>>>>> "z" == zdennis <zdennis@mktec.com> writes:

[#7463] Re: GC Question — zdennis <zdennis@...> 2006/03/01

ts wrote:

[#7467] Re: GC Question — ts <decoux@...> 2006/03/01

>>>>> "z" == zdennis <zdennis@mktec.com> writes:

[#7457] Re: GC Question — "H.Yamamoto" <ocean@...2.ccsnet.ne.jp> 2006/02/28

Hello.

[#7460] rails segfaults at 2nd load with eval.c: No such file or directory. — noreply@...

Bugs item #3683, was opened at 2006-02-28 10:33

1 message 2006/02/28

Re: [RCR] ruby --quiet; was Re: ANDCALL / iff? / &? (was Re: ruby-dev summary 28206-28273)

From: ara.t.howard@...

Date: 2006-02-07 16:11:56 UTC

List: ruby-core #7322

On Wed, 8 Feb 2006, Timothy J. Wood wrote:

>
> On Feb 7, 2006, at 7:05 AM, ara.t.howard@noaa.gov wrote:
>> i agree.  however -w should not be changed.  simply do
>> 
>>   $VERBOSE=nil
>> 
>> and you will get no warnings.  i use it often due to ruby's over-zealous
>> warnings
>
>  These two statements seem contradictory to me.  If -w is useful, then it
>  shouldn't be turned off.  If it isn't useful, then it shouldn't exist (or
>  should be fixed).

array bounds checking is useful - but it's often desirable to turn it off
because it hinders performance.  by that i mean to say that just because
something is useful under some circumstances does not mean that it is useful
in all circumstances.  specifically -w is not useful when world writable
directories are involved since programs of any significant length and
complexity will spew pages of warnings.  i write much code that is shared and
run by users who know nothing about ruby; when they see a page of warnings go
screaming by it's hardly confidence inspiring.  -w is useful to me during
development, but not to them in a production environment.

btw.  the RCR i made was essentially to modify -w to make it more useful, but
currently setting $VERBOSE directly is the way to get around it.

>  How about the same idiom as in gcc for this particular case?
>
> 	if a = b # warns
> 		...
> 	end
>
> 	if (a = b) # doesn't warn
> 		...
> 	end
>
>  Better yet have warnings be individually configurable:
>
> 	ruby -w # all warnings on
> 	ruby -w -wno_assign_in_conditional # everything but this warning
>
> 	# Or, at runtime...
> 	$WARNINGS[:assign_in_conditional] = false
>
>  I admit, I'm a warning zealot and compile my C code with '-Wall -Werror 
> -Weverything-not-included-inWall' ... :)

indeed.  a more complex warning scheme would be nice.

regards.

-a

-- 
happiness is not something ready-made.  it comes from your own actions.
- h.h. the 14th dali lama

Thread

Prev Next

In This Thread

Prev Next