Activity
From 05/26/2013 to 06/01/2013
06/01/2013
-
09:42 PM Bug #8471: パーセント記法とString #メソッドの組み合わせの戻り値が異常
- no6v (Nobuhiro IMAI) wrote:
> > 2番めと3番め、6番めと7番めをいろんな記号に置き換えてみると雰囲気がつかめるんじゃないでしょうか。
> ...
ご回答ありがとうございます。
すみませんおっしゃるとおりでした。
正常な動作です。 -
09:30 PM Bug #8471: パーセント記法とString #メソッドの組み合わせの戻り値が異常
- > 2番めと3番め、6番めと7番めをいろんな記号に置き換えてみると雰囲気がつかめるんじゃないでしょうか。
「2番めと3番め、6番めと7番めの % を」という意味でした。
$ ruby -rripper -rpp -ve 'pp Ripper.lex("%()%%!!.class")'
ruby 2.1.0dev (2013-06-01 trunk 41011) [x86_64-linux]
[[[1, 0], :on_tstring_beg, "%("]... -
- > 下記のコードを実行すると。''が戻ってきます。
> ...
これは false が返るんじゃないでしょうか？
> この戻ってきたものに対して各種メソッドを呼んでも''が返ってきます。
> ...
これは、%%% % %%%.class と解釈されて、%%% は %() などと同じく(空)文字列のリテラルで、
"" % xxx だと、xxx が(多分)何であろうと空文字列が返るので、特におかしなところはないと思います。
$ ruby -rripper... -
- ***再現手順
下記のコードを実行すると。''が戻ってきます。
(%%%%%%%).nil? => ''
上記ではnil?を取り上げましたが、
実際は全メソッドで''が戻ってきます。
この戻ってきたものに対して各種メソッドを呼んでも''が返ってきます。
%%%%%%%.class.class.class.class => ''
下記の環境で確認しています。
ruby 2.0.0p0 (2013-02-24 revision 39474)... -
07:04 PM Feature #8468: Remove $SAFE
- $SAFE is not a good security option for at least a few reasons:
* It requires maintaining checks for both tainting and safe levels in nearly *every* piece of C code attached to Ruby, including extensions. This is both a maintenance an... -
12:38 PM Feature #8468: Remove $SAFE
- One wonders where everyone has been for the last five months. The entire Rails security fiasco would have been avoided if DHH had seen fit to write Rails with $SAFE = 1. This is one thing that the Perl community got right almost immedi...
-
- JRuby has not supported $SAFE for a long time, and the only complaints we've heard are from people that thought they needed $SAFE (and did not) or people who just happened to notice it was missing.
We strongly support removing $SAFE, ... -
10:05 AM Feature #8468 (Closed): Remove $SAFE
- Yesterday, at GitHub Tokyo drinkup (thanks, GitHub!), Matz agreed to remove the $SAFE == 4 feature from Ruby 2.1.
Shibata-san, a developer of tDiary, which is the only application using $SAFE == 4, also agreed to remove it, so today is ... - 05:11 PM Revision bc7a6dbb (git): * 2013-06-02
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41025 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
05:11 PM Revision b285af64 (git): * enc/euc_jp.c: fix typo: the name of EUC-JIS-2004.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41024 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
02:43 PM Feature #8469 (Closed): ABI checker とか導入しませんか
- 最近 Vit が報告してきたように、193にもたまにABI非互換が入っているようです。
見たところ実害はなさそうなのですが、非互換が報告されてから実害の有無を検討するのは不毛なのでパッチリリース前に
機械的にチェックしたいですよね。ほとんどのケースは意図的な非互換だからOKという結論になるのだろうとは思いますが、
精神衛生上、枕を高くして寝れる度がちょっとだけ上がります。
で、ちょっと時間をとってみたところ、意外と簡単そう。
http://ispras... - 02:17 PM Revision 8b1b2638 (git): * vm_eval.c (rb_mod_module_eval): mention in docs that arguments passed
- to the method are passed to the block
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41023 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 09:01 AM Revision 6bdfe415 (git): * lib/set.rb (Set#freeze, taint, untaint): Save a "self" by
- utilizing super returning self, and add tests while at it.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41022 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
08:25 AM Revision 4a223fb6 (git): compile.c: not simple if keyword args
- * compile.c (iseq_set_arguments): not a simple single argument if any
keyword arguments exist. [ruby-core:55203] [Bug #8463]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41021 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * vm_insnhelper.c (vm_yield_setup_block_args): split single parameter
if any keyword arguments exist, and then extract keyword arguments.
[ruby-core:55203] [Bug #8463]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41020 b2dd03c8... -
- * vm_insnhelper.c (vm_yield_setup_block_args): break a long line and
add comments. remove useless code.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41019 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
02:25 AM Revision a10ea5b9 (git): remove duplicated entry
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41018 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * error.c (rb_exc_new_cstr): rename from rb_exc_new2.
* error.c (rb_exc_new_str): rename from rb_exc_new3.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41017 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * string.c (rb_str_new[2-5], rb_{tainted,usascii}_str_new2),
(rb_str_buf_new2): remove old interfaces.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41016 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 01:00 AM Revision 8663df2f (git): Restore the removed change-log entries
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41015 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
05/31/2013
-
- * ext/zlib/zlib.c (gzfile_read, gzfile_read_all, gzfile_getc),
(gzreader_gets): check EOF. [ruby-core:55220] [Bug #8467]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41014 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41013 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
10:32 PM Revision ce20b98b (git): * bignum.c: Use BDIGIT type for hbase.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41012 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41011 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Use Socket::Option#ip_multicast_loop and Socket::Option#ip_multicast_ttl
instead of Socket::Option#int because NetBSD's size is byte though
others' is int.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41010 b2dd03c8-39d4-4d8f-98ff-... -
- whose value's is byte.
* ext/socket/option.c (sockopt_byte): getter for above.
* ext/socket/option.c (inspect_byte): inspect for above.
* ext/socket/option.c (sockopt_s_ip_multicast_loop): constructor of
the sockopt whose optname is... - 04:59 PM Revision 1db20976 (git): * ext/bigdecimal/bigdecimal.c (BigDecimal_power): use rb_dbl2big
- to convert a double value to a Bignum.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41008 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
04:23 PM Feature #6183: Enumerator::Lazy performance issue
- @gregolsen Looks like some of this was applied, sorry I haven't had a chance to check it yet.
Could you check?
It may need a rebase, the patch didn't apply cleanly and some of the functions already exist (like append_method()) -
04:10 PM Bug #6550 (Closed): crash 1.9.3
- Close because this cannot be reproduced in ruby_1_9_3 branch.
- 03:24 PM Revision e337c7f9 (git): * 2013-06-01
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41007 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- representable in BDIGIT.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41006 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41005 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- (big2str_orig): hbase_numdigits argument added.
(big2str_karatsuba): Ditto.
(rb_big2str0): Calculate hbase_numdigits.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@41004 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- =begin
Try:
FooFoo.new.instance_exec('blah', &foo_putter)
=end
-
10:40 AM Feature #8465: Proc set_binding
- Oops, I meant that last line to say:
#I expect...
foo_putter.set_binding(FooFoo.new.foo_foo_proc.binding)
foo_putter.call("blah")
#to output:
# foo blah
-
- =begin
(({instance_eval})) is a solution to evaluate a proc in the binding of another object
but it is not a solution for a (({Proc})) that takes arguments
I propose that in order to suppor this use-case we need (({Proc#set_bindin... -
01:53 PM Feature #4254: Allow method transplanting
- thanks nobu! I blindly trusted the travis-ci build. good to know this is still valid behavior.
-
01:23 PM Bug #7092 (Rejected): StringScanner start-of-line matches false positives, while lookbehind for a newline gives false negatives
- I'm marking this ticket as closed due to no feedback.
--
Yusuke Endoh <[email protected]> -
- Sorry for late reply.
Anyway it is difficult to fix a bug if no one reproduces it.
I'm marking this ticket closed. Please reopen this if you could repro. Thanks.
--
Yusuke Endoh <[email protected]> -
- kosaki-san, what do you think?
--
Yusuke Endoh <[email protected]> -
- Now you are the release manager!
--
Yusuke Endoh <[email protected]>