unsuscribe

How to Unsubscribe

guide

guide

(unknown)

Unsubscribe

unsubscribed!

Re: Welcome to our (ruby-doc ML) You are added automatically

unsubscribe

2013/4/29, ruby-doc-admin <at> ruby-lang.org <ruby-doc-admin <at> ruby-lang.org>:
> Caution: If you reply this mail, the recipient is mailing list!
> post articles	<ruby-doc <at> ruby-lang.org>
> commands	<ruby-doc-ctl <at> ruby-lang.org>
> maintainer	<ruby-doc-admin <at> ruby-lang.org>
>
> Welcome to our mailing list <ruby-doc <at> ruby-lang.org> !
>
> This mail contains the fundamental usage of the mailing list server.
>
> 1	How to use this server
>
> Please send commands in the mail body not subject to the address
> <ruby-doc-ctl <at> ruby-lang.org>.
>
> The command syntax is as follows:
>
> 	help
>
> 	mget last:10 mp
>
> Please send the "help" to the address <ruby-doc-ctl <at> ruby-lang.org> for help
> and
> server functions overview
>
> 	help
>
> to get general information on this list
>
> 	guide
>
> If you want to make a contact with the mailing list maintainer, please
> e-mail to
>
> 	ruby-doc-admin <at> ruby-lang.org
>
> ML server exists to decrease routine works by maintainers. Please try
> to use server functions as could as possible.
>
> 				ruby-doc <at> ruby-lang.org Maintainer
> 				ruby-doc-admin <at> ruby-lang.org			
>
>
>

--

-- 
with respect<br>Yar
Skype : yar.snishko
yar <at> europe.com
100005747649169 <at> facebook.com

Re: Welcome to our (ruby-doc ML) You are added automatically

来自timelimit的邮件

Documentation Translations

Hello Everyone,

I had someone approach me earlier about helping out with Spanish translations of the Ruby documentation.
With that in mind I'd like to get a feel for what, if at any, progress has been made to translate the Ruby
documentation into something other than English (or Japanese if there is any untranslated
documentation). 

The objective of this is to try and get a documentation translation team together, and start to centralize
activity. Please respond on or off list if you have interest or know of existing translation projects.

Regards,
Chris White
http://www.twitter.com/cwgem

ObjectSpace#each_object example issue

The documentation for ObjectSpace#each_object has the following sample code:

 *     a = 102.7
 *     b = 95       # Won't be returned
 *     c = 12345678987654321
 *     count = ObjectSpace.each_object(Numeric) {|x| p x }
 *     puts "Total count: #{count}"
 *
 *  <em>produces:</em>
 *
 *     12345678987654321
 *     102.7
 *     2.71828182845905
 *     3.14159265358979
 *     2.22044604925031e-16
 *     1.7976931348623157e+308
 *     2.2250738585072e-308
 *     Total count: 7

In this case, c, with the value of 12345678987654321 is supposed to show for being a Bignum. However on 64 bit
systems this isn't the case:

= 64bit MacOSX Ruby SVN HEAD =
irb(main):001:0> puts RUBY_VERSION + " " + RUBY_PLATFORM + " " + RUBY_PATCHLEVEL.to_s
1.9.2 x86_64-darwin10.8.0 290
=> nil
irb(main):002:0> 12345678987654321.class
=> Fixnum

This won't show because as explained, "Immediate objects (Fixnums, Symbols true, false, and nil) are
never returned." One a 32 bit system, however, this isn't an issue:

= 32bit Ubuntu Ruby SVN HEAD
irb(main):001:0> puts RUBY_VERSION + " " + RUBY_PLATFORM + " " + RUBY_PATCHLEVEL.to_s
1.9.4 i686-linux -1
=> nil
irb(main):002:0> 12345678987654321.class
=> Bignum

I see two possible solutions to this:

1) Use a number that produces Bignum on both 32 an 64 bit systems:

irb(main):003:0> 12345678987654321094903903903.class
=> Bignum

2) Split out the explanation to show 32 and 64 bit side by side?

3) Just add a side not explaining the issue with 32 and 64 bit differences

Also there might be another potential fix if there is some constant that holds the min and max values Bignum
is capable of, but that's more of a feature request than a change in the docs.

- Chris
Twitter:  <at> cwgem
 		 	   		  

alias - error in documentation

All, 

I believe I found an error in the documentation for a ruby keyword - alias.

The documentation, under 1.9 keywords link=> alias, states that

p.full_name = "David"   # Please use fullname=

I believe the comment is incorrect. The full_name= is still referencing the old name= definition and not
the newly defined one. 

(I have of course verified my hypothesis by actually running the code.)

Hope this is useful, 

-Kalman Hazins