13037-15029

^ Treating Unicode specially (was: Re: \u escapes in string literals: proof of concept implementation)
13037 [duerst it.ao] This is one possibility. If we want to support Unicode well, then

^ unsubscribe
13042 [hrpoliveira ] <br>

^ Austin Ziegler's behaviour (Was: clarification of ruby libraries installation paths?)
13054 [lucas lucas-] Austin,
+ 13055 [luislavena g] Please Lucas, don't take that as example. Out-of-the-box on Windows
| 13064 [halostatue g] OpenSSL is included in the Ruby One-Click Installer. OUT OF THE BOX,
| 13066 [luislavena g] Austin, you're the one that every post/thread I start asking for
| 13094 [rick rickbra] Do we think that maybe, just maybe, things went off the rails when the
| + 13095 [luislavena g] Rick and everyone on this list: please excuse my reaction.
| | + 13097 [ml.chibbs gm] Yes, I agree with Rick, this has definitely gone off course.
| | + 13103 [mental rydia] There is, however, a lot of pent-up frustration in the Ruby community
| |   + 13116 [transfire gm] +1
| |   + 13134 [zimbatm oree] I think it would help, and not only for debian, if the rubygems team
| + 13121 [znmeb cesmai] Sheesh ... now it's about *Rails*? :)
+ 13063 [halostatue g] I don't submit Debian bugs because I don't use Debian. I have,

^ Re: Welcome to our (ruby-core ML) You are added automatically
13056 [rogerpack200] guide

^ new Enumerable.butfirst method
13069 [david davidf] Matz,
+ 13071 [transfire gm] Why not have a lazy range? Where you might currently do
| 13073 [david davidf] Because with an enumerable that does not provide random access like an
| 13091 [transfire gm] That's a very good point. But can we not "look ahead" n items?
| 13093 [transfire gm] Ah, never mind. We wouldn't be able to prevent side effects. So okay.
+ 13084 [matz ruby-la] I was not confident about my English description.  If it's OK, it's
  + 13086 [rfh atnet.at] why not have a head and tail (which could be one or more each) ..
  | 13087 [matz ruby-la] head is OK, but I think tails should take last n elements.
  + 13089 [dblack rubyp] I agree with David; it's not a good name. It sounds like one of these
  + 13104 [david davidf] Well tradition helps, but I think I'd still prefer another name.
    13120 [matz ruby-la] I abandoned #butfirst this time (just reverted).  Maybe after I
    + 13125 [david davidf] So that explains why take and drop return arrays instead of enumerators.
    + 13132 [transfire gm] How is that less confusing?
    | 13136 [rogerpack200] When you do bring it back in, one possible name would be
    + 13400 [artem.vorozt] Maybe    #take_if and #drop_if will be better?
      13401 [murphy rubyc] isn't that what they do?
      13402 [artem.vorozt] Thanks and sorry. :)

^ Didn't find String#subseq
13083 [ed.odanow wo] In http://eigenclass.org/hiki.rb?Changes+in+Ruby+1.9#l125 a method
13088 [matz ruby-la] We've never provided String#subseq.  It's a bug in the page.  We made
13157 [aff28 cam.ac] Could I request that there be a ruby String method that exposes this
+ 13158 [ed.odanow wo] Isn't it dangerous to allow direct access to byte indices of a utf-8 encoded
| 13159 [aff28 cam.ac] Yes. It would be a use-at-your-own-risk if-you-know-what-you're doing
+ 13160 [david davidf] class String
  13162 [ed.odanow wo] Here is exactly the problem possible I mentioned...
  13178 [matz ruby-la] We will provide a validation method, name not fixed yet.

^ 1.8.6 gc.c thoughts
13096 [rogerpack200] It seems that on a 'cpu intensive' program (one that generates a lot of
+ 13099 [matz ruby-la] It might be true.  The GC behavior is very difficult to expect in
| 14967 [rogerpack200] It might be worth encouraging someone to implement a new Ruby GC as
+ 14998 [brent mbari.] Roger,
  15029 [rogerpack200] It can only decrease if it wraps around, I think (since it's unsigned).

^ Re: clarification of ruby libraries installation paths?(Was: Austin Ziegler's behaviour (Was: clarification of ruby libraries installation paths?))
13105 [mblondel rub] This approach gives us the best of the two worlds. On one hand, if
13109 [halostatue g] Which is appreciated. Three years after it was asked for. :/

^ Future of Option "C" in String#unpack
13106 [ed.odanow wo] I have a question related to the future of the "C" option (and even "c") for
13119 [matz ruby-la] or=20
13126 [duerst it.ao] I think what should be changed is the description, then.

^ %s and utf8 ?
13107 [hadmut danis] I am printing string values with something like
13130 [duerst it.ao] This is a known and difficult problem. For a large character set
13133 [ed.odanow wo] Unfortunately it is even difficult in european context - my name is a good
13137 [now bitwi.se] form a
13138 [ed.odanow wo] Does it still exist, or is it planned/under development (I didn't find it)?

^ regular expressions in utf8?
13108 [hadmut danis] can utf8 characters be used in [] in regular expressions?
13111 [ed.odanow wo] It should work, and a test shows, that it works. I've used an utf-8 encoded file

^ Re: Debian package names
13117 [aredridel nb] +1 as well. PLD names them ruby-modules[sic] and ruby and ruby-

^ Enumerable#inject alias #fold?
13122 [murphy rubyc] Haskell has a method like the new Enumerable#reduce called "fold" (foldl
13124 [david davidf] I don't have an opinion about fold, but reduce is a well-known method

^ RDoc Horizontal Rule Error
13127 [nex342 gmail] Apologies if this isn't the right place for this.
13128 [vjoel path.b] This patch was included in 1.8.6, but not in 1.8.6p36.

^ patch for lib/net/http.rb, self['User-Agent'] ||= 'Ruby'
13135 [stephen.bann] I posted this patch before in the middle of another thread and didn't
+ 13140 [aaron tender] Sounds like a bug on the server side.  RFC2616 says that the User-Agent
| 13142 [stephen.bann] It's definitely a bug in the server implementation.
+ 13193 [aamine lover] OK, I have commited your patch in trunk (Ruby 1.9).
  13195 [akr fsij.org] I guess it will be forbidden by someone, like libwww-perl.
  13203 [stephen.bann] $ ruby -rnet/http -e 'Net::HTTP.start("www.google.com") {|h| p h.get("/search?q=foo", "User-Agent"=>"") }'
  13372 [akr fsij.org] I see.

^ Required Space for Unicode Character Attribute Tables
13139 [ed.odanow wo] I have a general question related to Unicode support in Ruby. Are there
13155 [duerst it.ao] All of the ICU data (see www.icu-project.org) is on the order of 10MB.
13156 [now bitwi.se] And contains a lot of junk we won't generally need.  My UTF-8 library
13165 [ed.odanow wo] This sounds very good.

^ 1.9 Prime class change request
13141 [erlercw gmai] In mathn.rb, please remove the method Prime.cache and its aliases,

^ Two Issues (open-uri's respond_to? and autoload's require)
13143 [transfire gm] I'd like to bring attention to two bugs in hopes the can be fixed in
13149 [nakahiro sar] On the first thought when I saw the request in rubygems-devel ML [1], I
13153 [transfire gm] Thanks. My problem isn't actually using gems. I have my own override.
13171 [nakahiro sar] Oh, I see.  Let's wait for RubyConf to be over and core developers will

^ Return Value of Encoding.find
13147 [ed.odanow wo] I'm not very happy with the behaviour of "Encoding.find". If the method is

^ hacking on the "heap" implementation in gc.c
13161 [lloyd hilaie] I've been playing (and that's all it is at this point) with the heap
+ 13163 [hgs dmu.ac.u] Glad people are looking at this....
| 13164 [lloyd hilaie] If these changes ever get seriously considered, I'm flexible on all
+ 13166 [sylvain.joye] Interesting. I also did an implementation of a fixed heap size (with a
+ 13177 [matz ruby-la] Pretty interesting idea, but we don't want to slow down Ruby by factor
| 13180 [lloyd hilaie] charset=US-ASCII;
| 13181 [matz ruby-la] Great.  I am not going to merge the patch to 1.8 soon, because 1.8 is
| 13190 [lloyd hilaie] I understand and respect your restraint toward destabilizing 1.8.  I
+ 13218 [pbrannan atd] Interesting work.  Reducing the memory footprint is usually a good thing
  13222 [lloyd hilaie] I agree with all of your points.  The testing does indeed lack rigor.
  13223 [pbrannan atd] I agree.  Ruby 1.9 does have some performance tests in the benchmark/
  13230 [znmeb cesmai] Well ... if it's just Ruby-implementation A vs. Ruby-implementation B,
  13240 [pbrannan atd] Yes, this is true.  It would be really nifty to see some percentiles and
  13241 [znmeb cesmai] I'm planning (assuming RubyForge approval) to break that chunk of the
  13242 [pbrannan atd] I don't think you've had enough punch to drink. :)
  13252 [znmeb cesmai] Punch? You sure that's not Kool-Aid? :)
  13345 [rogerpack200] I assume you mean a 'heap' data type?  Yeah might be nice :)

^ New Book: _The Ruby Programming Language_
13167 [david davidf] As you may know, I've been working on a Ruby book.  It is called _The

^ Possible flaw in CGI::Session
13170 [bas.van.klin] When creating a new session based on an incoming request without session_key

^ Thinking of dropping YAML from 1.8
13182 [shyouhei rub] As a branch manager I think I cannot maintain YAML lib any longer. No
+ 13183 [alexey.verkh] The whole point of a maintenance branch is "something that should not
| 13184 [james graypr] I have to agree that this is an extremely popular library.  This is a
| 13185 [ujwalic gmai] where to start ... to fix the YAML code bugs
| 13186 [vjoel path.b] Pick one!
| + 13187 [vjoel path.b] @@ -163,7 +163,7 @@
| | 13188 [vjoel path.b] Sorry, this is the corrected patch.
| + 13189 [transfire gm] Maybe it would be better to move YAML out, so that it will give
| | 13191 [ujwalic gmai] I'am reviewing the code ... YAML 1.1 spec
| + 13194 [djberg96 gma] Regards,
|   13197 [wilsonb gmai] I personally think YAML needs a rewrite, not a removal. The existing
+ 13192 [halostatue g] Removal of YAML will break RubyGems, at least 0.9.4.
+ 13211 [why ruby-lan] I want to say thankyou to shyouhei (and to matz, nobu, akr, many
  13269 [transfire gm] +1

^ Subscribe to list w/o email
13196 [transfire gm] I'm now using the ruby-core-google interface to this list, rather then
+ 13199 [now bitwi.se] ...
| 13200 [transfire gm] Oh, and I had read that too. I just forgot the information was in there. Thanks!
+ 13434 [now bitwi.se] Do you have any idea as to why I am unable to set my subscription to
  13435 [now bitwi.se] Damn mailing lists that set Reply-To.  Sorry everybody.

^ Ruby's Standard Library could use a lead maintainer
13198 [gregory.t.br] During the Town Hall meeting with Matz at RubyConf, I asked him
+ 13201 [drbrain segm] I think it is a big job for somebody who is not getting paid to do
| 13880 [Daniel.Berge] I'll second that. Would RubyCentral be willing to contribute to this
+ 13202 [james graypr] This is an interesting issue.  It will surely not be easy to address
  13204 [znmeb cesmai] Well, I think this is one of those, "Oh gosh yes ... that's a *really*
  13205 [gregory.t.br] Does anyone have some knowledge they can share of how different open
  13209 [znmeb cesmai] well, I think the R community does a pretty good job, but it's been
  13210 [transfire gm] On Nov 4, 10:31 pm, "M. Edward (Ed) Borasky" <zn...@cesmail.net>
  13212 [znmeb cesmai] apt-get for Debian, yum for Fedora and emerge for Gentoo. The difference
  13221 [brent mbari.] I think the problem of maintaining the large set of bundled libraries
  + 13224 [gregory.t.br] I'm not suggesting a lead stdlib maintainer actually maintain all the
  + 13225 [ed.odanow wo] There are situations when this behavior will cause problems. In the meantime I
    13227 [gregory.t.br] l be
    13228 [ed.odanow wo] Is't something like the following scenario possible (may be even now)?
    13229 [luislavena g] T24gMTEvNS8wNywgV29sZmdhbmcgTsOhZGFzaS1Eb25uZXIgPGVkLm9kYW5vd0B3b25hZG8uZGU+
    13881 [hramrach cen] T24gMDYvMTEvMjAwNywgTHVpcyBMYXZlbmEgPGx1aXNsYXZlbmFAZ21haWwuY29tPiB3cm90ZToK

^ guessutf 1.0.0 released
13206 [ed.odanow wo] Dear Ruby designers, developers, and testers!
+ 13207 [ed.odanow wo] Now it works - I don't know why.
+ 13239 [ed.odanow wo] Because of possible extensions I would like to hear your opinions. I want to
  13263 [now bitwi.se] On Nov 6, 2007 5:20 PM, Wolfgang N=E1dasi-Donner <ed.odanow@wonado.de> wrot=
  + 13266 [ed.odanow wo] Are these modules already available via Ruby-Forge (or another place)? - I ask,
  + 13318 [ed.odanow wo] Do you have some heuristics or links to articles about to guess which of the

^ Kernel#p
13213 [transfire gm] Quick query about Ruby 1.9. Does Kernel#p return it's arguments or no?
13214 [celtic sairy] irb(main):001:0> RUBY_VERSION
13216 [transfire gm] On Nov 5, 6:36 am, Arlen Christian Mart Cuss <cel...@sairyx.org>

^ Auto-translating gateway between ruby-core and ruby-dev?
13215 [charles.nutt] I for one feel left out of conversations on ruby-dev. Barring my
+ 13217 [lucas lucas-] Yes!
+ 13219 [ed.odanow wo] "Yes" + "!"*1000
+ 13220 [murphy rubyc] it will be so funny ^^
  13232 [duerst it.ao] Good point. If you want to do this, please create separate lists
  13274 [steven lumos] Right.  A literal two-way translation would put undue burden on the

^ The future of VM::InstructionSequence
13237 [vincent.isam] I had some free time and there was a mail on ruby-dev that might be of

^ performance problem in 1.9
13238 [pbrannan atd] Checked latest 1.9 out of svn last week to run this test.
13243 [murphy rubyc] this is because the new encoding-aware methods are not optimized for
+ 13246 [pbrannan atd] This doesn't explain, however, why execution duration increases
| + 13248 [ed.odanow wo] Is it possible that it has a relationship with my remark about identifying
| | 13256 [duerst it.ao] The character counting problem you describe exists, but not for US-ASCII,
| | 13260 [ed.odanow wo] I think it should be recognized, if an encoding has fixed size characters, so
| | 13287 [duerst it.ao] Yes. Ruby is open source, so you can check for yourself.
| | 13291 [ed.odanow wo] You are right, but I wouldn't trust myself there. I didn't write complex C
| + 13249 [murphy rubyc] strange. is it the generate.rb or the test.rb that's slowing down?
|   13250 [pbrannan atd] Good catch - I thought I was running generate.rb under 1.8.2 under both
+ 13257 [duerst it.ao] This is not true. Many of them are indeed optimized for ASCII,
  + 13261 [ed.odanow wo] I would like to say, people want Ruby 1.9 more powerful than Ruby 1.8, which
  + 13272 [murphy rubyc] I'll try to do benchmarks for all common string methods this weekend.

^ [PATCH]:  Parse floating point literals that start with a dot
13244 [brent mbari.] This is a multi-part message in MIME format.
13271 [Daniel.Berge] =20

^ invoke_method calling private methods when invoked on integers
13245 [david davidf] *     1.invoke_method(:puts, "hello")  # causes NoMethodError
13255 [nobu ruby-la] It needs to access VM flags, I guess.

^ send can't call protected methods, but invoke_method can
13254 [david davidf] With the current builds I can't call a protected method with send, but I
13258 [nobu ruby-la] HTH.
13277 [david davidf] Nobu,
13278 [matz ruby-la] Yes, please.

^ Frightening retry behavior should be deprecated and removed
13259 [charles.nutt] $a = 0
+ 13302 [brabuhr gmai] me@linux 1> cat z.rb
+ 13319 [nobu ruby-la] It's gone away in 1.9.
+ 13320 [matz ruby-la] Since this feature is removed from 1.9, you can officially ignore this.
  13325 [david davidf] It appears that retry can still do its magic re-evaluate the expression
  + 13332 [charles.nutt] snippit for the RubySpec wiki...
  | 13342 [david davidf] Ask me again when I've got my book wrapped up!
  | 13380 [charles.nutt] I shall...when will that be? :)
  + 13333 [evan falling] Given the fact that retry in a method is gone, I believe we should
    13338 [james graypr] It seems like it could come in handy in an iterator, along the lines =20

^ Patch for uClibc stdio - status?
13262 [B.Candler po] Is there any chance of getting this patch either committed or explicitly

^ invoke_method, and things you "just have to know"
13265 [dblack rubyp] I see that send! is gone from 1.9, and send is back to calling private
13267 [pbrannan atd] I disagree.  When I see the name "invoke_method" I expect it to use the
13268 [dblack rubyp] I think a lot about what's involved in teaching people Ruby -- which,

^ Should "Iconv" work with the actual Ruby 1.9 snapshots?
13270 [ed.odanow wo] Good Evening!
13279 [duerst it.ao] I have been using iconv with up-to-date builds of 1.9 on a regular
13348 [rogerpack200] Yeah did you install the mingw port of iconv?  It can be a little
13350 [ed.odanow wo] I've already found it and will follow the instructions. This weekend I will

^ Patch to 1.8.6 resolv.rb
13273 [gwtmp01 mac.] At RubyConf I got motivated to help out on documentation.  I dove
13802 [gwtmp01 mac.] With the recent discussion about Ruby documentation [ruby-talk:280883]
13821 [matz ruby-la] I'd love to merge it.  But could you please turn of your automatic

^ Problem with installing latest version
13283 [duerst it.ao] I just tried to compile and install the latest SVG revision, 13837.
+ 13284 [david davidf] Martin,
+ 13285 [david davidf] I've just checked in a fix.  Please svn update and try again.
  13286 [duerst it.ao] The problem seems fixed. Thanks for your help!     Martin.

^ Unrecovered memory leak thoughts.
13288 [rogerpack200] So it seems from my trivial analysis that there are instances when
13293 [rick.denatal] Well, most (all?) garbage collection approaches don't guarantee that
13296 [pbrannan atd] I question how significant reference counting would be compared to
+ 13298 [znmeb cesmai] Well ... there have been probably *thousands* of CS papers written on
| 13309 [rogerpack200] Not an extremely big (code-wide) amount of overhead: the equivalent of
| 13337 [rogerpack200] If Ruby were to switch to a smarter GC style, at large landmarks might
| 13341 [znmeb cesmai] As I noted earlier, there are probably thousands of CS papers on garbage
+ 13346 [rogerpack200] And possibly decrement with their finalizers, and provide a traverse