[#39810] 2.0 feature questionnaire — SASADA Koichi <ko1@...>
I made a questionnaire "What do you want to introduce in 2.0?" in my
2011/10/1 SASADA Koichi <[email protected]>:
Hi,
On Sun, Oct 2, 2011 at 1:30 AM, Yukihiro Matsumoto <[email protected]> wro=
Oops, I was mentioned.
See below.
(10/07/2011 02:19 PM), Evan Phoenix wrote:
>> No, it isn't. =A0MVM-aware extensions shall obey the MVM-safe APIs.
2011/10/1 SASADA Koichi <[email protected]>:
On Monday, October 24, 2011 at 10:29 PM, Charles Oliver Nutter wrote:
On Mon, Oct 24, 2011 at 10:29 PM, Charles Oliver Nutter <[email protected]
On Tue, Oct 25, 2011 at 3:51 PM, Rocky Bernstein <[email protected]> wrote:
On Tue, Oct 25, 2011 at 1:51 PM, Rocky Bernstein <[email protected]>wrote:
[#39823] Discussion results — SASADA Koichi <ko1@...>
Hi,
I did not have the fortune of attending the discussion, but I would
Hi,
Hello Matz,
Hello,
On Mon, Oct 3, 2011 at 8:16 AM, Yusuke Endoh <[email protected]> wrote:
How does String#margin behave when given irregular input?
On Mon, Oct 3, 2011 at 11:05 AM, Jim Freeze <[email protected]> wrote:
Sent from my iPad
On Mon, Oct 3, 2011 at 1:52 PM, Gmail <[email protected]> wrote:
On Mon, Oct 3, 2011 at 14:16, Yusuke Endoh <[email protected]> wrote:
[#39824] Road to 2.0 — SASADA Koichi <ko1@...>
Hi,
Hello,
[#39886] [Ruby 1.9 - Bug #5393][Open] some style fixes in enum.c docs — b t <redmine@...>
[#39888] [Ruby 1.9 - Feature #5394][Open] Anonymous Symbols, Anonymous Methods — Kurt Stephens <ks.ruby@...>
[#39915] [Ruby 1.9 - Feature #5400][Open] Remove flip-flops in 2.0 — Magnus Holm <judofyr@...>
Hello,
[#39918] [Ruby 1.9 - Bug #5401][Open] Ruby 1.9.3 interpreter crash — Conrad Taylor <conradwt@...>
[#39937] redmine 2.0 tracker — SASADA Koichi <ko1@...>
There is no 2.0 tracker (sub-project) in redmine.
[#39957] [Ruby 1.9 - Bug #5407][Open] Cannot build ruby-1.9.3-rc1 with TDM-GCC 4.6.1 on Windows XP SP3 — Heesob Park <phasis@...>
[#39986] problems with Refinements — Shugo Maeda <shugo@...>
Hi,
There are also the group of people that think refinements are just a
Hi,
> Unfortunately, I missed Brian's talk, so we have to wait until the
Hi,
> I am not sure why
[#39993] [Ruby 1.9 - Feature #2348] RBTree Should be Added to the Standard Library — David Graham <david.malcom.graham@...>
(2011.10.07 01:50 ), David Graham wrote:
On 07/10/2011, at 1:16 PM, Kenta Murata wrote:
(2011/10/07 1:50), David Graham wrote:
On Thu, Oct 6, 2011 at 6:34 PM, SASADA Koichi <[email protected]> wrote:
[#40058] Statistical Profiling — Perry Smith <pedzsan@...>
Would it be plausible to somehow, get the (ruby) stack of the running =
[#40073] [Ruby 1.9 - Feature #5427][Open] Not complex patch to improve `require` time (load.c) — Yura Sokolov <funny.falcon@...>
[#40117] [Ruby 1.9 - Bug #5437][Open] Using fibers leads to huge memory leak — Robert Pankowecki <robert.pankowecki@...>
[#40172] plans for 2.0. — Carter Cheng <cartercheng@...>
Hello,
2011/10/17 Carter Cheng <[email protected]>:
[#40188] [Ruby 2.0 - Feature #5454] keyword arguments — Yukihiro Matsumoto <matz@...>
This looks very interesting=21 Would someone be willing to translate to e=
Hi,
Hi,
Thanks for the translation=21
RnJvbSB0aGUgY3VycmVudCBwYXRjaCBpdCBzZWVtcyB0byBtZSB0aGF0IHRoaXMgd291bGQgcmFp
[#40200] [Ruby 1.9 - Bug #5459][Open] Silence -Wmissing-declarations and -Wold-style-definition warnings in mkmf — Nikolai Weibull <now@...>
[#40203] invoking garbage_collect in gc.c — Carter Cheng <cartercheng@...>
Hello,
[#40259] Counseling — Perry Smith <pedzsan@...>
Ruby and I are back in counseling... Its always the same thing with =
What's your $LC_CTYPE? What OS are you on?
Hi all,
Gon軋lo Silva wrote:
On Oct 21, 2011, at 9:43 AM, Perry Smith wrote:
To try and cut to the core of the issue: in Ruby 1.8 it was common practi=
> What Ruby needs (IMHO), is the equivalent of Obj-C's NSData class. That is,
On Saturday, October 22, 2011 at 12:43 PM, Jon wrote:
[#40271] Can rubygems save us from "binary-compatibility hell"? — Yusuke Endoh <mame@...>
Hello, rubygems developers --
Forwarding this again to ruby-core as received a postmaster delivery failur=
Hello,
On Thu, Nov 10, 2011 at 4:38 PM, Yusuke Endoh <[email protected]> wrote:
Hello,
2011/11/10 Yusuke Endoh <[email protected]>:
Hello,
Dne 22.10.2011 4:48, Yusuke Endoh napsal(a):
On Oct 31, 2011, at 2:41 PM, V=EDt Ondruch wrote:
Dne 1.11.2011 0:05, Eric Hodel napsal(a):
On Nov 1, 2011, at 2:03 PM, V=EDt Ondruch wrote:
[#40281] [Ruby 2.0 - Bug #5470][Open] r33507 and r33508 break the build under MinGW — Luis Lavena <luislavena@...>
[#40284] set_trace_func changed? — Intransition <transfire@...>
Did something change about `set_trace_func` between 1.8.7 and 1.9.3?
[#40290] [ruby-trunk - Feature #5474][Assigned] keyword argument — Yusuke Endoh <mame@...>
Hi,
Hi,
See below.
Hi,
> |> It's Python way, and I won't take it.
More refinement below. I think we're on a good path here.
Hi,
On Wed, Oct 26, 2011 at 2:08 PM, Yukihiro Matsumoto <[email protected]>wrote:
Hi,
On Wed, Oct 26, 2011 at 7:30 PM, Yukihiro Matsumoto <[email protected]> wr=
Hi,
On Thu, Oct 27, 2011 at 3:16 AM, Nobuyoshi Nakada <[email protected]> wrot=
Hi,
[#40311] [ruby-trunk - Feature #5478][Open] import Set into core, add syntax — Konstantin Haase <Konstantin.Haase@...>
On 2011-12-04, at 16:15:00, Alexey Muranov wrote:
[#40312] [ruby-trunk - Feature #5479][Open] import StringIO into core, add String#to_io — Konstantin Haase <Konstantin.Haase@...>
On Tue, Oct 25, 2011 at 10:14:54PM +0900, Charles Nutter wrote:
My main request was to add String#to_io, as Aaron described, so this protoc=
On Wed, Oct 26, 2011 at 02:22:21AM +0900, Haase, Konstantin wrote:
[#40314] [ANN] 2011 Call for grant proposals — Shugo Maeda <shugo@...>
Hello,
Hello,
> Ruby reference manual for you, me and everyoneApplicant: Yutaka Hara
[#40316] [ruby-trunk - Feature #5481][Open] Gemifying Ruby standard library — Hiroshi Nakamura <nakahiro@...>
On Tue, Oct 25, 2011 at 14:45, Intransition <[email protected]> wrote:
[#40322] [ruby-trunk - Feature #5482][Open] Rubinius as basis for Ruby 2.0 — Thomas Sawyer <transfire@...>
Come back when all 1.9 features and callcc are implemented :-)
(2011/10/25 12:46), Yusuke Endoh wrote:
On Mon, Oct 24, 2011 at 9:58 PM, SASADA Koichi <[email protected]> wrote:
On Tue, Oct 25, 2011 at 11:45 PM, Tim Felgentreff <[email protected]> wrote:
[#40356] JIT development for MRI — Carter Cheng <cartercheng@...>
Hello,
Hello Charlie,
Hi,
Dear Koichi SASADA,
I noticed that you used context threading in YARV. Do you have some analysis
Thanks for reference.
Thanks Koichi.
On Wed, Oct 26, 2011 at 6:43 PM, Carter Cheng <[email protected]> wrote:
Hi Carter,
Thanks Koichi. How do profiling based approaches differ from trace recording
[#40412] [ruby-trunk - Bug #5486][Open] rb_stat() doesn’t respect input encoding — Nikolai Weibull <now@...>
On Fri, Oct 28, 2011 at 07:28, Usaku NAKAMURA <[email protected]> wrote=
On Fri, Oct 28, 2011 at 08:14, Nikolai Weibull <[email protected]> wrote:
On Sun, Mar 11, 2012 at 22:41, Nobuyoshi Nakada <[email protected]> wrote:
Hello,
2012/3/15 U.Nakamura <[email protected]>:
[#40427] cfp consistency error — Aaron Patterson <tenderlove@...>
Hi, I'm getting a cfp consistency error when I use trunk ruby. Here is
[#40453] Test case format — Jon <jon.forums@...>
I see no mention of a required (or preferred) test case format after reviewing:
2011/10/27 Jon <[email protected]>:
[#40489] [ruby-trunk - Bug #5497][Open] Math.log10(10_000) error on HP-UX/PA — The Written Word Inc <bugs-ruby@...>
[#40492] [ruby-trunk - Feature #5505][Open] BasicObject#__extend__ — Thomas Sawyer <transfire@...>
[#40527] [ANN] Ruby 1.9.3-p0 is out — "Yuki Sonoda (Yugui)" <yugui@...>
-----BEGIN PGP SIGNED MESSAGE-----
Hello,
On Sun, Oct 30, 2011 at 11:11 PM, Luis Lavena <[email protected]> wrote:
On Sun, Oct 30, 2011 at 11:20 AM, Yugui <[email protected]> wrote:
> On Sun, Oct 30, 2011 at 11:20 AM, Yugui <[email protected]> wrote:
[#40562] [ruby-trunk - Bug #5525][Open] UDPSocket#bind(ip, port) fails under IPv6 => Errno::EAFNOSUPPORT — Iñaki Baz Castillo <ibc@...>
[#40571] [ruby-trunk - Bug #5529][Open] Bus error with Fibers on OSX Lion — Dave Thomas <dave@...>
[#40586] [ruby-trunk - Feature #5531][Open] deep_value for dealing with nested hashes — Kyle Peyton <kylepeyton@...>
[ruby-core:40360] Re: [ruby-trunk - Feature #5481] Gemifying Ruby standard library
On 25/10/11 at 22:43 +0900, Yusuke Endoh wrote: > Hello, > > 2011/10/25 Lucas Nussbaum <[email protected]>: > > Instead, I would prefer a plan where the interpreter no longer releases with the stdlib, but just releases with a "core lib". Then the user would install the stdlib as a set of gems. > > I cannot understand your issue. > Even if we release core+stdlib as a big package, you can split > the package to each deb package. Doesn't it work? Let me try to rephrase more clearly. There are several places different sets of software that are or could be developed independently in the Ruby ecosystem. - interpreters (+ core libs) - standard library - third-party gems The problem is: how do we maintain and release interpreters and standard library? There are two sides to this question: - how do we avoid stdlib code duplication between interpreters? - how do we encourage stdlib development? I think that the cleanest solution is to consider MRI and the stdlib to be two completely different projects, with their own release cycles, their own security support, etc. That way: - people working on the interpreters can focus on the interpreters - people working on the stdlib can focus on the stdlib - there's no code duplication There are two problems with that solution: - it requires each stdlib release to be well tested on the supported interpreters, possibly taking into account past releases of the interpreters. - there could be a problem during the installation. We need to bootstrap a ruby installation so that there's enough of stdlib installed to run rubygems and install the remaining gems. That can easily be solved by providing a full snapshot of stdlib. But then it needs to stay a snapshot, and everybody should be expected to be able to use a newer version of each lib. With the current proposal, I see two ways for Debian to package Ruby (and none of them are really good): - provide a bundle of stdlib + mix of updated gems as a single package. That means that Debian maintainers will have to choose which version to include for each gem, and the user won't be able to do it. - split the stdlib into a very large number of small packages for each lib, so that each one can be updated separately. A prerequisite for this solution is that we know beforehand how to split the stdlib. (The root problem with Debian is that two packages cannot provide the same file if they can be installed together. So we can't have a package replacing/overriding only a part of another package.) Lucas