larskanis (Lars Kanis) wrote: The current setting is a major interoperability issue and it is neither useful nor expected, because nobody seriously uses the ancient locale dependent cpXYZ encodings for file content. Come Japan and check Japanese Windows users' text files :) If a native encoding shall be used, it should be UTF-16 on Windows. However UTF-16 would make interoperability and compatibil
I think it will be usefull to have function that convert input string as it was written in prime qouted string or in double qouted string. It's part of metaprogramming. Example: class String # Create new string like it will be writed in qoutes. Optional argument define type of qouting used: true - prime qoute, false - double qoute. Default is double qoute. def unescape prime = false eval( prime ?
I am the creator of the Contributor Covenant, a code of conduct for Open Source projects. At last count there are over 13,000 projects on Github that have adopted it. This past year saw adoption of Contributor Covenant by a lot of very large, very visible projects, including Rails, Github's Atom text editor, Angular JS, bundler, curl, diaspora, discourse, Eclipse, rspec, shoes, and rvm. The bundle
I would like to suggest a phased transition across several releases in Ruby 2.x (the specific version numbers and flag names are just examples): In Ruby 2.3, it is possible to turn on warnings when mutating a String literal (--warn-frozen-strings). the warnings come with the place in the source where the String was originally created In Ruby 2.4 (or 2.5?), the warning is on by default Once it is o
=begin The same result with psych. $ ruby -v -ryaml -e 'YAML::ENGINE.yamler = "psych"; s="한글";pYAML.load(YAML.dump(s))==s' ruby 1.9.3dev (2010-11-02 trunk 29667) [i686-linux] /usr/local/lib/ruby/1.9.1/psych/deprecated.rb:79: warning: method redefined; discarding old to_yaml_properties /usr/local/lib/ruby/1.9.1/syck/rubytypes.rb:13: warning: previous definition of to_yaml_properties was here false
Solaris10にて、r50900 以降、 TestParallel::TestParallel#test_jobs_status TestParallel::TestParallel#test_separate のいずれか、または両方で、テストが停止状態となり次に進まなくなります。 スレッドのデッドロックが発生しているような感じです。 ところで、こういう場合の上手いデバッグ方法って何があるでしょうか?
This might be a bug exposed due to r36944 ("avoid unnecessary select() calls before doing I/O") which I don't want to revert. Does the following fix it? --- a/ext/socket/init.c +++ b/ext/socket/init.c @@ -400,12 +400,6 @@ rsock_connect(int fd, const struct sockaddr *sockaddr, int len, int socks) status = (int)BLOCKING_REGION_FD(func, &arg); if (status < 0) { switch (errno) { case EINTR: -#if defin
以下のプログラムは if intrap == 1 raise "trap nested" end が真になってしまって例外終了してしまうのですが、これは起きてはいけないのではないでしょうか。 以下の二点が問題だと考えます。 1)このプログラムのようにシグナルを連続して配送されるとスタックオーバーフローを引き起こせる 2)Rubyレベルでsigprocmask()に相当するシグナルブロッキング操作が提供されていないため、 正しいトラップハンドラを書くのが、ほぼ不可能になっている C言語ですら、シグナルハンドラ実行中はシグナルが自動的にマスクされるんですから、Rubyでも 同レベルの配慮はMRIがおこなうべきだと思います。 n = 0 intrap = 0 parent = $$ trap(:USR1) { if intrap == 1 raise "trap nested" end intr
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く