19748-21854

19582-21708 subjects 19938-21072

[Feature #729] curly brackets" and "begin end" blocks should behave syntactically and semantically exactly the same
19748 [redmine@ru y] Feature #729: curly brackets" and "begin end" blocks should behave syntactically and semantically exactly the same
19783 [pbrannan@at ] Except for precedence, the curly brackets are the same as do..end, not

[Feature #729] curly brackets" and "begin end" blocks should behave syntactically and semantically exactly the same
19749 [redmine@ru y] Issue #729 has been updated by Michael Klishin.

[Bug #730] Infinite recursion on 'super' in dynamically generated modules
19750 [redmine@ru y] Bug #730: Infinite recursion on 'super' in dynamically generated modules

[Bug #731] Net::HTTPHeader []= method does not work as expected
19751 [redmine@ru y] Bug #731: Net::HTTPHeader []= method does not work as expected

[Feature #729](Rejected) curly brackets" and "begin end" blocks should behave syntactically and semantically exactly the same
19752 [redmine@ru y] Issue #729 has been updated by Yukihiro Matsumoto.

Reporting issues in RedMine impossible
19753 [hramrach@ce ] Since I received notification about the old rubyforge tracker being
19754 [yugui@yu ui ] You can probably use redmine without JavaScript.
19835 [hramrach@ce ] Well, you can. It looks like reporting and viewing issues is possible.

[Bug #734] "no superclass method" raised when calling super from an aliased method included from a module (when method was aliased from inside the module)
19755 [redmine@ru y] Bug #734: "no superclass method" raised when calling super from an aliased method included from a module (when method was aliased from inside the module)

google is messing my students up :P
19756 [ryand-ruby@z] if you search for <<ruby download>> on google the top hit is this
+ 19772 [rogerpack200] +1 on disliking the fact that that old page shows up so much in google
+ 19782 [pbrannan@at ] By referencing the url in an email that gets indexed by google, you may

[Bug #704] delegate.rb will only delegate to specifically-named delegate object
19758 [redmine@ru y] Issue #704 has been updated by Erik Hollensbe.

Proposal: Method#get_args
19759 [wycats@gm il] ...
+ 19764 [chiology@gm ] ...
+ 19768 [halostatue@g] Why a tuple, aside from being what's provided by the ParseTree API? I
| 19775 [meinrad.rech] ...
| 19776 [halostatue@g] Yes. I think that would possibly help handle the case of the mandatory
| 19777 [B.Candler@po] A Struct perhaps? You can always use to_a to get a tuple back.
| 19778 [dave@pr gp o] Or an array of strings?
| 19779 [halostatue@g] That feels a little better from my ability to understand it, but then
| 19780 [dave@pr gp o] Actually, I'm not convinced there's any extra work compared to
| 19830 [charles.nutt] It's actually an array of arrays with a set structure; I tend to like
+ 19769 [matz@ru y- a] As I said in person at the conference place, I am positive about the
| + 19786 [hongli@pl n9] How about calling it "parameters"? The argument is the value that gets
| + 19827 [nobu@ru y- a] * how to represent default arguments. They can be arbitrary
| | + 19831 [charles.nutt] For the JRuby args support (and I believe the ParseTree support) we
| | + 19842 [pbrannan@at ] Control structures are tricky but not impossible to decompile.  For example,
| |   19930 [nobu@ru y- a] But the code cut off from the context has no meanings.
| |   19937 [pbrannan@at ] Do you have an example?
| |   19950 [nobu@ru y- a] The code to set default value accesses the local variable, that
| |   19966 [pbrannan@at ] I want to make a distinction between the code and the representation of
| + 19832 [charles.nutt] Someone else suggested "parameters", which isn't too bad. "arguments"
+ 19771 [rogerpack200] Some of this functionality is available currently via
| 19833 [charles.nutt] * The parse tree needs to be standardized or frozen
| 19844 [pbrannan@at ] I disagree.  The parse tree can be presented to the user as an
| + 19848 [wycats@gm il] Sent from my iPhone
| + 19850 [charles.nutt] Doesn't matter if there's a guarantee. People will write to the MRI or
+ 19781 [pbrannan@at ] I like this idea, but I would rather see an object returned rather than
+ 19787 [rogerpack200] The only question I have is why would one want to know the names of
| + 19788 [hongli@pl n9] Merb uses it to map HTTP parameters to method parameters.
| + 19789 [transfire@gm] One could use it for documenting external interfaces. Eg. A command
|   19790 [rogerpack200] Thinking out loud, would also be nice to have access to the
|   + 19806 [halostatue@g] Is RubyVM::InstructionSequence considered portable?
|   | 19808 [rogerpack200] Works for me in Linux, win32, and OS X, so...I'd imagine wherever MRI
|   | 19809 [halostatue@g] What I meant is whether it's meant to be portable among interpreters.
|   | 19811 [rogerpack200] Oh I'm favor of it--I would however suggest that allowing for
|   | + 19813 [wycats@gm il] ...
|   | | 19815 [rogerpack200] I agree that a simpler implementation (like one that didn't include
|   | + 19834 [charles.nutt] Docstrings for sure. I've lobbied for such in the past, but never had
|   + 19807 [jeremymcanal] ruby_parser gives you this with the #comments method.
|     19836 [charles.nutt] FWIW, I fully support parse tree-based tooling that is *offline*, i.e.
+ 19818 [mikael@ho lu] Allow me to throw in my ~.116892074 DKK;
| + 19822 [pbrannan@at ] If we had unbound procs, it could be represented as an unbound proc.
| | 19839 [charles.nutt] Yeah, I don't even know how that would work; block bodies are parsed
| + 19837 [charles.nutt] Strongest argument I've seen for a real class. I'm more in favor of that
|   19838 [dave@pr gp o] Before this all grows to some large API, I was wondering: what actual
|   19870 [B.Candler@po] 1. the names of the arguments
|   + 19871 [B.Candler@po] Hmm.
|   | + 19876 [Thomas.Enebo] I question the validity of Arity for this case since the arity is really 3.
|   | | 19879 [B.Candler@po] class Foo
|   | | + 19880 [charles.nutt] I think arity is nearly meaningless when argument lists perform
|   | | + 19884 [Thomas.Enebo] Yes I guess I can accept arity 2...though you still need three arguments
|   | + 19906 [dev@me ne .c] Don't you think we're overthinking this all?
|   + 19874 [pbrannan@at ] Or a rest or block argument.
|     19881 [charles.nutt] I'm leaning toward a wholly array-based structure that specifies all
|     + 19882 [halostatue@g] foo(a, b = 2, *c, &block)
|     | 19886 [charles.nutt] Representationally I'd say it's a wash...using hashes would not really
|     | 19897 [halostatue@g] [ruby-core:19779]
|     | + 19898 [charles.nutt] Righto...yep, I see where you're coming from, but I don't think it gains
|     | + 19916 [B.Candler@po] The main problem with this, to me, is that it's a Perl object :-)
|     |   19917 [transfire@gm] Don't fear the OOP.
|     + 19883 [wycats@gm il] I am strongly in favor of this proposal. Getting something simple that
|     | 19941 [matz@ru y- a] * symbol for block argument should be :block, or anything else?
|     | 19942 [matz@ru y- a] what if the default value for an optional argument is more than a simple
|     | 19947 [nobu@ru y- a] Since :expr is a valid expression, I don't think it is
|     | + 19955 [wycats@gm il] Agreed. What we need is a special sentinel value (I originally =20
|     | + 19956 [rogerpack200] AFAIK this isn't possible in Ruby currently (though might work fine
|     | | 19957 [wycats@gm il] In our case, we're dealing with inbound web params, so the defaults
|     | | 19958 [wycats@gm il] ...
|     | + 20029 [wycats@gm il] ...
|     |   20085 [matz@ru y- a] The most realistic implementation is one from Nobu in
|     |   20107 [wycats@gm il] ...
|     |   20112 [matz@ru y- a] Nakada-san, could you check in?
|     + 19887 [pbrannan@at ] #<Parameters params=[
|       19889 [charles.nutt] At that point I think we gain very little over arrays of arrays, since
|       + 19891 [pbrannan@at ] That depends on what what you want to do with the structure.
|       + 19892 [jim.weirich@] (1) I can ask parameter.required?  rather than parameter.first
|         19893 [jdeville@mi ] It could also behave like an array with Enumerable, each and :[] defined. I=
|         19894 [B.Candler@po] I can see the reasoning behind having a Parameter class (although I still
|         19895 [jim.weirich@] Not sure you could do #2 (convenient :to_s method) in that case.
|         19896 [charles.nutt] I think I'm going to stick to my guns. I have full respect for the
|         19899 [jim.weirich@] <nod> And I'm not too happy with the required?/optional? suggested
|         + 19900 [halostatue@g] I reiterate my suggestion to return a positional array of hashes. ;)
|         + 19915 [B.Candler@po] That does give me an idea. Since "?" is not legal in a variable name, then a
+ 20304 [paul.mcmahon] I am late to this discussion, but I am a bit concerned about the
  20306 [dev@me ne .c] Actually, it returns [:opt, param_name, default_value], but default
  20308 [B.Candler@po] I suppose it could also (but currently can't) access mandatory parameters
  20309 [radek.bulat@] class MyArray
  20311 [B.Candler@po] Indeed, and you could already do

ThreadGroup: << and Enumerable for POLS
19760 [paddor@gm il] Hey
19761 [matz@ru y- a] I am negative.  ThreadGroup do not have any iterating method.  Just
19766 [vjoel@pa h. ] It would lead to race conditions, wouldn't it?
19774 [paddor@gm il] Thanks for answering.

[Bug #714](Closed) Socket bug in Ruby-mswin32
19762 [redmine@ru y] Issue #714 has been updated by Usaku NAKAMURA.

[Bug #738] Repeated calls to popen cause thread problems
19763 [redmine@ru y] Bug #738: Repeated calls to popen cause thread problems
+ 20867 [akr@fs j. rg] "IO::for_fd analyzer.fileno" in testt.rb is dangerous.
| 21850 [hramrach@ce ] Note that the descriptor is closed by the reading thread after it is
+ 21853 [charles.nutt] Required in what version of JRuby? I'm running your testt2 script on
  21854 [charles.nutt] ...fine.

[Bug #704] delegate.rb will only delegate to specifically-named delegate object
19765 [redmine@ru y] Issue #704 has been updated by Yukihiro Matsumoto.

[Bug #649] Memory leak in a array assignment?
19770 [redmine@ru y] Issue #649 has been updated by Roger Pack.

[Bug #405] ssl.rb:31: [BUG] Bus Error
19773 [redmine@ru y] Issue #405 has been updated by Evan W.

Status of copy-on-write friendly garbage collector
19784 [hongli@pl n9] I'm wondering what the current status is of making the GC copy-on-write
19799 [authornari@g] This topic may be connected with me.
+ 19804 [rogerpack200] I wonder if something similar could be used for is_pointer_to_heap.
+ 19812 [wycats@gm il] ...
| 19823 [matz@ru y- a] Last month, I saw a research presentation on mostly copying garbage
| + 19824 [wycats@gm il] ...
| | 19828 [charles.nutt] I'm curious how compaction could even be added while keeping extension
| | 19904 [shugo@ru y- ] Mr. Ugawa is working for that.  His implementation is based on Bartlett's
| + 19901 [hongli@pl n9] Is the presentation or other material online? I'm interested in reading it.
|   19905 [matz@ru y- a] I am afraid that it's only in Japanese.
|   + 19907 [duerst@it ao] In case you have a pointer, can you give it anyway?
|   | + 19908 [matz@ru y- a] It will be published in IPSJ PRO journal within several months (if
|   | + 19936 [admin@ha th ] As for Japanese only material ---
|   + 19909 [shyouhei@ru ] ...
|     19910 [kurt@ca hn t] AFAIK, the BDW collector can be configured to do mostly-copying
|     + 19911 [shyouhei@ru ] (I'm not the author so apology in advance for my being not familiar with
|     + 19912 [matz@ru y- a] * current GC is more portable than BDW GC.
+ 20118 [rogerpack200] I wonder if this would work well with the 'multi processed' GC patch
| 20121 [matz@ru y- a] Which one?  The one with forking before starting GC?  If so, it is
| 20171 [rogerpack200] Yeah the one with forking before starting GC [which is...itself a
+ 20481 [rogerpack200] I assume that it works now, and was merged into trunk?
  20497 [matz@ru y- a] ...

[Feature #739] Regexp#match with position
19785 [redmine@ru y] Feature #739: Regexp#match with position
19797 [nobu@ru y- a] MatchData#begin.

[Bug #740] bigdecimal rounding errors in 1.8.x
19791 [redmine@ru y] Bug #740: bigdecimal rounding errors in 1.8.x

[Bug #740] bigdecimal rounding errors in 1.8.x
19792 [redmine@ru y] Issue #740 has been updated by Roger Pack.

am I missing something for windows non blocking?
19794 [rogerpack200] irb(main):008:0> a = File.new 'a', 'w'
19801 [usa@ga ba ec] Windows does not support nonblocking I/O on file.
19803 [rogerpack200] Perhaps the docs could be reflected to update this fact.

file's not flushing then sizing in win32
19795 [rogerpack200] Some people have run into the bug in win32 where writing to a temp
19800 [usa@ga ba ec] How I reproduce the problem?
19940 [rogerpack200] require 'tempfile'

[Bug #741] 1.9.1-preview1 uri/generic.rb #check_path L484 bug/typo
19805 [redmine@ru y] Bug #741: 1.9.1-preview1 uri/generic.rb #check_path L484 bug/typo

[Bug #703] string output duplication occurs if the same file descriptor written to in different threads
19810 [redmine@ru y] Issue #703 has been updated by Roger Pack.

[Bug #721] select in windows accepts too many fd's
19814 [redmine@ru y] Issue #721 has been updated by Roger Pack.

[Bug #721](Closed) select in windows accepts too many fd's
19816 [redmine@ru y] Issue #721 has been updated by Usaku NAKAMURA.

Re: Definition of "Support levels", 1.9.1 supported platforms and recruitment for platform maintainers
19819 [lists@da sa ] Can we add OpenSolaris as one of the supported platforms? I can

[Bug #742] 1.9.1-preview1 build fails on Mac OS X 10.4
19820 [redmine@ru y] Bug #742: 1.9.1-preview1 build fails on Mac OS X 10.4

[Feature #739] Regexp#match with position
19825 [redmine@ru y] Issue #739 has been updated by Jeremy Stephens.

[Bug #741](Closed) 1.9.1-preview1 uri/generic.rb #check_path L484 bug/typo
19826 [redmine@ru y] Issue #741 has been updated by Yukihiro Matsumoto.

is this design...intentional?
19843 [rogerpack200] p = proc do |arg|
19856 [charles.nutt] In 1.8 "proc" means "lambda" and "lambda" can be returned from. I think
19867 [B.Candler@po] In 1.9, proc has been changed so it's an alias for Proc.new rather than

[Bug #743] Socket.gethostbyname returns odd values
19845 [redmine@ru y] Bug #743: Socket.gethostbyname returns odd values

[Bug #744] memory leak in callcc?
19846 [redmine@ru y] Bug #744: memory leak in callcc?
19903 [brent@mb ri ] Roger,
19913 [brent@mb ri ] Roger,

[Bug #745] IO associates with the file descriptor, not the stream
19851 [redmine@ru y] Bug #745: IO associates with the file descriptor, not the stream

[Bug #719] yaml not precise on some strings
19857 [redmine@ru y] Issue #719 has been updated by Patrik Wenger.

[Bug #746] typo in help
19858 [redmine@ru y] Bug #746: typo in help
19861 [matz@ru y- a] It's the default value for -W without level, i.e.
19869 [ryand-ruby@z] -w              turn warnings on for your script (modify verbosity
19914 [paddor@gm il] Yes, this is more clear.

[Bug #740](Closed) bigdecimal rounding errors in 1.8.x
19866 [redmine@ru y] Issue #740 has been updated by Yukihiro Matsumoto.

[Bug #743] Socket.gethostbyname returns odd values
19868 [redmine@ru y] Issue #743 has been updated by Brian Candler.

Date.parse("m/d/y") now treated as "d/m/y"?
19872 [dblack@ru yp] irb(main):001:0> RUBY_VERSION
19875 [kbloom@gm il] You're not looking at the whole behavior of Ruby 1.9
19877 [dblack@ru yp] Thanks for connecting the dots -- I'd been rather mindlessly looking

Splat nil
19873 [pbrannan@at ] I'm seeing differing behavior on 1.8 and 1.9.  Is this intentional?
19994 [pbrannan@at ] The last case is no longer hanging with the latest trunk; I don't know
19995 [binary42@gm ] [*some_collection_or_single_object_or_nil]

[Bug #704] delegate.rb will only delegate to specifically-named delegate object
19878 [redmine@ru y] Issue #704 has been updated by Erik Hollensbe.

[Feature #749] String#indent,  String#tabto, etc.
19885 [redmine@ru y] Feature #749: String#indent,  String#tabto, etc.

[Bug #719] yaml not precise on some strings
19888 [redmine@ru y] Issue #719 has been updated by Yui NARUSE.

[Bug #721] select in windows accepts too many fd's
19890 [redmine@ru y] Issue #721 has been updated by Roger Pack.
19902 [usa@ga ba ec] I solved only the problem that the reproduction script had shown.

Enumerator::Yielder
19918 [B.Candler@po] The block form of Enumerator in 1.9 introduces a new wrapper object,

[Bug #752] YAML::load has problems with older dates
19919 [redmine@ru y] Bug #752: YAML::load has problems with older dates

[Bug #752] YAML::load has problems with older dates
19920 [redmine@ru y] Issue #752 has been updated by David Welton.

flay is so awesome!
19921 [ryand-ruby@z] I just found a typo in code in tk via flay! RAD!! This exists in trunk
19922 [pit.capitain] Really impressive, Ryan! Do you know of similar tools for Java?
+ 19923 [ryand-ruby@z] nope. but the paper that I got inspiration from was working on C, so
| + 19924 [meinrad.rech] ...
| | 19963 [aaron@te de ] Aaron Patterson
| + 19931 [pit.capitain] Thanks, Ryan. Maybe someday I'll give this a try.
+ 19925 [spencer.rine] There is Simian - http://www.redhillconsulting.com.au/products/simian/ -
  19926 [ryand-ruby@z] Umm... Actually... flay kicks simian's ass. :P

Re: {Proc,Method}#parameters (Re: Proposal: Method#get_args)
19927 [nobu@ru y- a] It's simplest.
+ 19928 [charles.nutt] The original proposal also asked for literal defaults to be present. I'm
| + 19929 [nobu@ru y- a] but I can't the answer from the original poster. Or I'm
| + 19933 [B.Candler@po] True - but it's not clear if, or how, the literal defaults are used in merb.
|   19934 [wycats@gm il] def action(bar=1, baz=2); end
|   19935 [B.Candler@po] Ugh. Now I understand; instead of using Ruby's built-in default handling,
|   19939 [wycats@gm il] You were on the mark when you said it was a poor man's named args.
|   19943 [radek.bulat@] WWVodWRhLCBob3cgZG8geW91IGhhbmRsZSBkZWZhdWx0IHZhbHVlcyBsaWtlIHRoaXM/CgpjbGFz
|   19954 [wycats@gm il] We don't need non-simple values. Something like :expr would work me
+ 19932 [B.Candler@po] Probably not. Maybe ["a", "()"], otherwise ["a", nil] as you propose.
threads.html
top