[#21039] Happy new year and... moving Ruby development to Git? — Michael Klishin <michael.s.klishin@...>
Happy new year everyone.
On Jan 1, 2009, at 6:42 AM, Michael Klishin wrote:
On Thu, Jan 1, 2009 at 11:22 AM, James Gray <james@grayproductions.net> wrote:
brabuhr@gmail.com writes:
Quoting Michael Klishin <michael.s.klishin@gmail.com>:
Hi,
-----BEGIN PGP SIGNED MESSAGE-----
T24gRnJpLCBKYW4gMiwgMjAwOSBhdCAxMjoxOCBQTSwgRmxvcmlhbiBHaWxjaGVyIDxmbG9AYW5k
My opinion:
My two cents:
Eust=E1quio Rangel wrote:
On Sat, Jan 3, 2009 at 21:40, M. Edward (Ed) Borasky <znmeb@cesmail.net> wrote:
Nikolai Weibull wrote:
On Sat, Jan 3, 2009 at 10:39 PM, M. Edward (Ed) Borasky
Giuseppe Bilotta wrote:
On Sun, Jan 4, 2009 at 12:14, Joel VanderWerf <vjoel@path.berkeley.edu>wrote:
Michael Klishin wrote:
On Mon, Jan 5, 2009 at 12:29 PM, Michael Klishin
On 05.01.2009, at 16:10, Rados=C5=82aw Bu=C5=82at wrote:
On Mon, Jan 05, 2009 at 10:22:49PM +0900, Michael Klishin wrote:
-----BEGIN PGP SIGNED MESSAGE-----
On Mon, Jan 5, 2009 at 10:06 AM, Florian Gilcher <flo@andersground.net>wrote:
T24gTW9uLCBKYW4gNSwgMjAwOSBhdCA4OjA4IEFNLCBNZWlucmFkIFJlY2hlaXMKPG1laW5yYWQu
On Jan 1, 2009, at 04:42 AM, Michael Klishin wrote:
On Sat, Jan 3, 2009 at 00:34, Eric Hodel <drbrain@segment7.net> wrote:
On Sat, Jan 3, 2009 at 4:48 AM, Michael Klishin
On Sat, Jan 03, 2009 at 12:48:09PM +0900, Michael Klishin wrote:
-----BEGIN PGP SIGNED MESSAGE-----
On Mon, Jan 5, 2009 at 4:59 PM, Florian Gilcher <flo@andersground.net> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
On Mon, Jan 5, 2009 at 6:45 PM, Florian Gilcher <flo@andersground.net> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
On Jan 2, 2009, at 17:25 PM, Nikolai Weibull wrote:
> I think I'm entitled to an opinion on the subject because I am a
On Jan 6, 2009, at 12:16 PM, Brent Roman wrote:
On Wed, Jan 07, 2009 at 04:03:12AM +0900, James Gray wrote:
Hi,
[#21094] [Bug #975] ruby curses extension does not support multibyte characters — Michal Suchanek <redmine@...>
Bug #975: ruby curses extension does not support multibyte characters
[#21097] [Bug #977] caller for all threads patch — Roger Pack <redmine@...>
Bug #977: caller for all threads patch
I made a patch to Thread#caller(lev=1). It may be more flexible than
One thing I think might be cool is rather than raising an error for a
On Mon, Jun 8, 2009 at 5:06 PM, SASADA Koichi<ko1@atdot.net> wrote:
[#21180] how to use git to work with MBARI patches — Stephen Bannasch <stephen.bannasch@...>
At 3:16 AM +0900 1/7/09, Brent Roman asked in a previous thread about git:
[#21181] ruby_version changes in 1.9.1-rc1 — "Luis Lavena" <luislavena@...>
Hello All,
[#21238] [Bug #996] IRB doesn't work anymore with ruby-1.9.1-rc1 on MinGW — Chauk-Mean PROUM <redmine@...>
Bug #996: IRB doesn't work anymore with ruby-1.9.1-rc1 on MinGW
[#21244] [Bug #999] SSL & ZIP missing from ruby-1.9.1-preview1-i386-mswin32 — William Mason <redmine@...>
Bug #999: SSL & ZIP missing from ruby-1.9.1-preview1-i386-mswin32
Issue #999 has been updated by Luis Lavena.
[#21259] Do I need a special build arg to get irb to accept utf characters on OSX — Dave Thomas <dave@...>
I'm seeing very strange behavior at the irb prompt with ruby 1.9.1 =20
On 1/11/09 1:06 PM, Dave Thomas wrote:
[#21269] [Bug #1005] Strange behaviour of File.directory? under Windows — Alex Fortuna <redmine@...>
Bug #1005: Strange behaviour of File.directory? under Windows
[#21289] MRI 1.8.6 bug - exit is ignored if ensure clause throws exception which is caught by outer rescue — Shri Borde <Shri.Borde@...>
The following code snippet does print "after foo" when using MRI 1.8.6 on W=
[#21302] [PATCH] drastically improve rb_waitpid for short-lived children — Evan Phoenix <evan@...>
This evening I wrote this patch while helping a friend diagnose why,
[#21309] Current status of 1.9.1 RC2 — "Yugui (Yuki Sonoda)" <yugui@...>
-----BEGIN PGP SIGNED MESSAGE-----
[#21315] Proc-as-Binding is out again? — Charles Oliver Nutter <charles.nutter@...>
1.8 can use a proc as a binding:
It seems to be more interface based rather than disallowing the access
[#21339] [Bug #1010] Ruby-1.9's rake sh doesn't work on Windows (but fix provided) — Chauk-Mean Proum <redmine@...>
Bug #1010: Ruby-1.9's rake sh doesn't work on Windows (but fix provided)
Issue #1010 has been updated by Chauk-Mean Proum.
[#21345] [Bug #1011] Chinese GB18030 transcoding is breaking build at r21509 — Luis Lavena <redmine@...>
Bug #1011: Chinese GB18030 transcoding is breaking build at r21509
[#21383] [Bug #1019] irb/xmp fails because StringInputMethod doesn't support #encoding — Dave Thomas <redmine@...>
Bug #1019: irb/xmp fails because StringInputMethod doesn't support #encoding
[#21399] Proposal: Module#copy_method — Yehuda Katz <wycats@...>
I'd like it to be possible to copy methods from one module to another. The
2009/1/18 Yehuda Katz <wycats@gmail.com>:
Excerpts from Pit Capitain's message of Sun Jan 18 11:23:48 +0200 2009:
Yehuda Katz wrote:
AOP requires being able to hook into method dispatch, which either requires
Yehuda Katz wrote:
So I guess the question is... what's wrong with the implementation ;)
Yehuda Katz wrote:
Just FYI, the define_method version fails if your method requires the use of
I believe that methods (and blocks defined as methods via method_defined) a=
Hi,
Hi,
Yukihiro Matsumoto wrote:
Hi,
For my use-case, it would be ok to support copying methods to ANY module,
On Tue, Jan 20, 2009 at 10:15, Yehuda Katz <wycats@gmail.com> wrote:
[#21444] ruby 1.9 hashes, etc. — "Roger Pack" <rogerdpack@...>
I noticed in the NEWS file that 1.9 has more compacted hashes--does it then
On Mon, Jan 19, 2009 at 10:20 PM, Roger Pack <rogerdpack@gmail.com> wrote:
[#21448] [PATCH] Allow building ruby with mingw — Alexey Borzenkov <snaury@...>
---
[#21454] [Feature #1027] Dir.home — Kazuhiro NISHIYAMA <redmine@...>
Feature #1027: Dir.home
Hi,
Excerpts from Nobuyoshi Nakada's message of Wed Jan 21 05:19:23 +0200 2009:
[#21458] Repost: Evaluation order of block pass versus arguments — Charles Oliver Nutter <charles.nutter@...>
I posted this nearly a year ago and never got any replies. I'm reposting
[#21460] Array concat loops sometimes taking large amounts of "system" time. — Ron Mayer <rm_rails@...>
On both ruby1.8 and ruby1.9, about half the time when I run loops like this:
[#21473] Time.gm give me ArgumentError out of range (ruby 1.8.6 (2007-09-24 patchlevel 111) [i486-linux]) — Claudio Fiorini <claudio@...>
Hi all,
[#21492] 2 small warning fixes for 1.9.1 — Marcus Rueckert <darix@...>
hi,
[#21495] [Bug #1033] wrong documentation for Kernel#catch — Patrik Wenger <redmine@...>
Bug #1033: wrong documentation for Kernel#catch
[#21550] [Feature #1046] request: ability to run without specifying .rb — Roger Pack <redmine@...>
Feature #1046: request: ability to run without specifying .rb
Issue #1046 has been updated by Roger Pack.
Hi,
>
Hi,
> |Oh sorry--I meant that you would probably find my answer [that I am lazy and
[#21552] [Feature #1047] request: getters, setters for the GC — Roger Pack <redmine@...>
Feature #1047: request: getters, setters for the GC
I agree that something in this direction should be done.
Issue #1047 has been updated by Yusuke Endoh.
[#21570] [Bug #1057] ripper does not compile with mingw — Charlie Savage <redmine@...>
Bug #1057: ripper does not compile with mingw
[#21598] [Bug #1060] mkmf refuses to find 3rd party extensions - ruby 1.9.1 trunk — Charlie Savage <redmine@...>
Bug #1060: mkmf refuses to find 3rd party extensions - ruby 1.9.1 trunk
[#21605] Couple questions about testing Ruby interpreters — Michael King <kingmt@...>
I am trying to apply Brent's MBARI patches to Ruby 1.8.7 p72 to Ruby 1.8.6
[#21613] [Bug #1063] in `write': Not enough space - <STDOUT> (Errno::ENOMEM) on Windows XP — Nick Gorbikoff <redmine@...>
Bug #1063: in `write': Not enough space - <STDOUT> (Errno::ENOMEM) on Windows XP
Issue #1063 has been updated by Tinco Andringa.
[#21618] UID Too Big, A Bug? — James Gray <james@...>
Is this a bug in Ruby?
[#21640] [Bug #1068] Ruby Cannot Handle Some UIDs — James Gray <redmine@...>
Bug #1068: Ruby Cannot Handle Some UIDs
On Wed, Jan 28, 2009 at 05:00:05PM +0100, James Gray wrote:
Hi,
On Thu, Jan 29, 2009 at 08:53:38AM +0100, Nobuyoshi Nakada wrote:
Ondrej Bilka wrote:
On Jan 29, 2009, at 3:43 AM, Urabe Shyouhei wrote:
On Thu, Jan 29, 2009 at 8:33 AM, James Gray <james@grayproductions.net>wrote:
On Jan 29, 2009, at 7:57 AM, Rocky Bernstein wrote:
On Thu, Jan 29, 2009 at 9:04 AM, James Gray <james@grayproductions.net>wrote:
One small edit I'm sorry I can resist since after all this *is* a
[#21701] [Feature #1081] add File::write() convenience method — Suraj Kurapati <redmine@...>
Feature #1081: add File::write() convenience method
Issue #1081 has been updated by Yusuke Endoh.
Hi,
Hi,
Is it intended that the length of the leading nulls are not included
Hi,
>> Is it intended that the length of the leading nulls are not included
Hi,
Teamwork. :-)
2010/3/6 Run Paint Run Run <runrun@runpaint.org>:
[#21702] [Feature #1082] add Object#singleton_class method — Suraj Kurapati <redmine@...>
Feature #1082: add Object#singleton_class method
Issue #1082 has been updated by Suraj Kurapati.
Hi,
> We haven't met any consensus of a name for the method.
+1 for Eigenclass
+1 for metaclass, as is it compatible with ActiveSupport, Rubinius and _why=
Hi,
Hi,
Hi,
On Mon, Jan 4, 2010 at 9:41 PM, Yukihiro Matsumoto <matz@ruby-lang.org> wro=
Hi --
Hi,
On 23.02.10 08:14, Shugo Maeda wrote:
Hi,
Issue #1082 has been updated by Yusuke Endoh.
Hi,
[ruby-core:21592] Re: [Bug #744] memory leak in callcc?
Roger, With native threading, each thread gets its own private stack managed by the OS. So, yes, in Ruby 1.9, there should not be any ghost references from one thread's stack creeping onto another's. However, there is still the potential for ghost object references within any given thread's stack. GC.limit= determines that number of bytes that will be allocated (or reallocated) before a garbage collection pass is automatically triggered. It defaults to 8e6 bytes. I set it to 2e6 bytes on memory limited embedded targets. The process size will "breathe" by this amount of bytes while Ruby runs. Some might want to breathe deeper (and less often) if they've got bigger lungs. GC.limit is documented in ri as such. It is the primary GC tunable. If someone introduces a free list limit, they can call it GC.freelist_limit. I'm would not be confused by that. Nonetheless, if a couple more folks complain, I'll change GC.limit to something longer. I expect that it will get renamed in any case if it makes it into the thrunk. - brent Roger Pack wrote: > > On Mon, Jan 19, 2009 at 1:15 AM, Brent Roman <brent@mbari.org> wrote: > >> >> Yuki and Roger, >> >> I'm glad to hear these patches are working out well for you. > > > I assume that with 1.9 this style patch isn't as necessary as threads > don't > "share garbage" between each other--is that right? [each thread could > still > clean itself, but at least they don't share garbage between threads--is > that > right?] > > Also I might recommend renaming GC#limit to GC#malloc_limit or > GC#alloc_limit since "limit" is somewhat ambiguous--is it a limit to the > number of free pointers it will use? malloc size? [that type of thing]. > Thanks so much! > -=r > > -- View this message in context: http://www.nabble.com/-ruby-core%3A19846---Bug--744--memory-leak-in-callcc--tp20447794p21679891.html Sent from the ruby-core mailing list archive at Nabble.com.