48482-58263

48250-48891 subjects 48593-50133

WAY off topic... scheme for windows?
48482 [michael_s_ca] All the ruby talk recently about what language after ruby, the
+ 48498 [bobx@li ux a] Just open up the GOOGLE search engine and type SCHEME for WINDOWS and I
+ 48533 [tsiivola@cc ] Scheme has no canonical interpreter. Try MzScheme, I recall it works fine
| 48579 [quixote72@ho] I'de second that.
+ 48543 [nat.pryce@b1] You might find something here: http://www.schemers.org/

̤𢨡
48488 [support@ei e] <>()Ԥܼ

Ruby won't build on Jaguar
48493 [canyonrat@ma] I  know just enough about GNU make to wonder why anyone uses it instead
+ 48497 [bobx@li ux a] Isn't 1.6.7 in Jaguar already?
| 48499 [rich@in oe h] Yes, but statically compiled w/out a shared library for the interpreter.
+ 48500 [cjack@cj ck ] Darwin 6.x declares sys_nerr (Darwin 5.x did not). As a workaround, you
  48501 [hisa@im sy o] RubyCocoa distribution contains same patch in misc directory.
  48507 [canyonrat@ma] Thanks so much, Fujimoto. At least I know how to apply a patch.

next statement
48494 [DDouthitt@cu] ...
48495 [airboss@no e] Of course you did -- were you expecting ruby to automagically figure
48496 [airboss@no e] Er, sorry; I'm really not this stupid. I am, of course, referring to
48607 [nobu.nokada@] list.each { |entry|

Ruby/DL with GTK gtk_signal_connect
48521 [transami@tr ] have a problem. i dont know how to get gtk_signal_connect to reference a
48534 [ttate@kt ja ] How about `DL.callback'? It assigns a Proc object to a callback function.
48536 [transami@tr ] thank you, thank you, thank you! worked like a champ! :)
48539 [ttate@kt ja ] Thank you very much,

GridFlow 0.6.1
48523 [matju@sy pa ] Here is a new release of GridFlow (a multi-dimensional dataflow processing
48525 [transami@tr ] could you tell us a little more about what GridFlow is, and what it is
48529 [matju@sy pa ] In-reply-to: *

Hi
48524 [jim@fr ez .o] I saw your post about your Ruby presentation and looked

Best GC for Ruby?
48544 [justinj@mo i] Which method of garbage collection would most suit Ruby?
+ 48552 [billtj@y. lu] Thanks for all the sophisticated ideas regarding the next Ruby GC.
| 48555 [justinj@mo i] It sounds like all you want is the ability to register/unregister your own
+ 48566 [szegedy@no p] What is it?
| 48568 [justinj@mo i] A remembered set is a set of pointer locations that record which pointers
+ 48571 [matz@ru y- a] It will be
  + 48612 [justinj@mo i] I had a good look at the Boehm GC.  The only down side that I could see is
  | + 48671 [rc@va ca er ] FYI, check out http://www.ravenbrook.com/project/mps/
  | + 48919 [matz@ru y- a] See "7.5 Inter-generational pointers".  In p.172, "Using bytes rather
  |   + 48931 [justinj@mo i] Yes, I've read that very chapter.  If setting a pointer only results in a
  |   | + 48937 [billtj@y. lu] Please excuse me on my lack of knowledge regarding the GC model.  When we
  |   | | 48956 [justinj@mo i] Marking is the process of flagging live data.  When using C/C++, it's common
  |   | + 48961 [matz@ru y- a] For the current Ruby implementation, all attribute changes are done
  |   + 48955 [dan@si he or] Out of curiosity, have you given this a shot to see how performance
  |     + 48957 [mikkelfj-ant] Take a look at the papers posted for ocaml garbage collection. It is quite
  |     + 48960 [matz@ru y- a] Generational GC performs quite well if there are bunch of live
  |     | + 48966 [dan@si he or] Bummer--I'd hoped you had a good solution to my existing problem. :)
  |     | | 48967 [matz@ru y- a] Life is not that easy as always. ;-)
  |     | + 49125 [billtj@z. lu] I agree in principle of making the best for the average cases.  However,
  |     |   49130 [matz@ru y- a] Depends on each VM implementation.  JVM specification does not require
  |     |   + 49132 [pbrannan@at ] For that matter, we don't really need a garbage collector in Ruby
  |     |   + 49143 [billtj@z. lu] This is very interesting.  Therefore, just from the GC overhead point of
  |     |     49146 [pbrannan@at ] 'double' is already 64 bits, and so won't fit, unless we do some nasty
  |     |     49156 [billtj@z. lu] Well, currently int is usually 32 bits and most pointers are 32 bits and
  |     |     49177 [pbrannan@at ] There is a standard (ieee 754), but not everyone uses it.  There are
  |     |     49181 [billtj@z. lu] Well, then it seems that I have to wait until 128-bit pointer is common,
  |     |     + 49185 [pbrannan@at ] Yes, it's a LOT more complicated.
  |     |     + 49192 [szegedy@t- n] In the current implementation of Ruby, there are 2**31 possible
  |     |       49266 [billtj@y. lu] Yes, you are correct.  I am just playing with philosophy regarding the
  |     + 48964 [justinj@mo i] I think I need to allocate a bit of time for experimenting to see just what
  |       48989 [billtj@z. lu] It seems that the example shows the convenience of bringing in the power
  + 48620 [justinj@mo i] I had a good look at the Boehm GC.  The only down side that I could see is
    50179 [billtj@z. lu] Just some information that I got when I was searching how other

.bin & .b2h
48553 [jzakiya@ma l] In "The Ruby Way" on p.80

How to return path when doing directory recursion?
48557 [keuler@po ta] All-
48560 [alan@di ik t] Isn't it f?
48563 [shanko_date@] How about using the file.path method ;-)
48580 [keuler@po ta] Thanks Alan and Shashank. I'll check out your advice.

gethostbyname() requires reverse lookup to work?
48558 [pbrannan@at ] We ran into a problem last night where we could ping a host, telnet to
48559 [decoux@mo lo] pigeon% less socket.c
+ 48567 [bilotta78@ho] Is this the reason why Ruby needs an /etc/hosts with
+ 48692 [djberg96@at ] Couldn't you simply check RES_USE_INT6 and call gethostbyname or
  48711 [decoux@mo lo] RFC 2553
  48736 [djberg96@at ] Ok, but the question I have to ask is whether or not this actually affects
  48847 [pbrannan@at ] The ideal solution, I think, is to use a resolver library that uses

[ANN] YAML.rb 0.40 -- Circular references, Emitter enhancements
48564 [yamlrb@wh th] Aha!  A new YAML.rb is out at long last: >
48693 [dsafari@pa a] _why,
48728 [ruby-talk@wh] Yeah, it works out I guess.

how to create a ruby object via the c-api?
48565 [matthias_vei] how is it possible to create a certain ruby object via the c-api?
48603 [nobu.nokada@] You can use rb_reg_new().
48625 [billtj@y. lu] objects.  However, if you just want to do simple translation from Ruby to
48717 [matthias_vei] Thanks for all ideas and suggestions - I don't really thought about maintenance,

FXRuby Threading Problem Solved?
48573 [lyle@kn lo y] All,
+ 48574 [lyle@kn lo y] (... replying to myself ...)
| 48606 [nobu.nokada@] It was identified and suggested by Tietew.
| 48621 [lyle@kn lo y] OK. Many thanks to Tietew for identifying the problem!
| 48624 [curt@hi bs c] I just tested FreeRIDE (which suffered from the Threading problem under
| 48631 [curt@hi bs c] Looks like I jumped the gun on this one.
| 48713 [nobu.nokada@] Could you explain about that bug in detail?
+ 48576 [lyle@kn lo y] Yes, this fix has been back-ported to the Ruby 1.6 CVS branch (just
  48578 [rich@in oe h] Cool and cool!

ANN: Additional FXRuby installer for Ruby 1.7.3
48575 [lyle@kn lo y] All,

Newbis question - Pre-defined classes & modules
48581 [tran55555@ya] I am new in Ruby. Do not like to check the C source code.
48600 [gsinclair@so] I'm no expert myself, but I'd guess most, if not all, of the built-ins are

[ANN] RDE0.9.7.0 released
48582 [QZS01353@ni ] RDE 0.9.7.0 released.

suggestions to the Ruby community
48584 [stibbs@no ha] other language i use (perl, python, PHP, javascript, and now ruby). Others
+ 48585 [mgushee@ha e] Python's module index? I'm also a Python user, but I'm not sure what
| 48587 [stibbs@no ha] sorry for not being more specific.
+ 48586 [dan@si he or] More to the point, someone should get in touch with the CPAN folks.
+ 48588 [james@ja es ] What is that? Could you describe it for those of us not that familiar with
| 48589 [mgushee@ha e] Oh, *that* module index. I thought you meant something else.
+ 48590 [lyle@kn lo y] lists a considerable number of English-language books. "Programming
| + 48594 [tim@ve et .a] Between the paragraphs at the bottom of this page and the links
| + 48595 [stibbs@no ha] Not to sound rude, but as i stated in my first post "Please take into
|   + 48598 [tim@ve et .a] _THAT_ won't happen.
|   | 48604 [stibbs@no ha] Ground control to major tim, can you hear me? I don't think so. I do
|   | 48608 [tim@ve et .a] [ top-posting fixed ]
|   + 48609 [ptkwt@sh ll ] OK, so what kinds of topics should future Ruby books (of either the
|   | + 48637 [james@ja es ] It may be a god place to list these ideas.
|   | | 48645 [DDouthitt@cu] ...
|   | | 48654 [alwagner@tc ] The American version:  "Any jackass can kick down a barn, but it takes a
|   | + 48667 [stibbs@no ha] In my original post i thought i made it clear that i am referring to the
|   | + 58249 [stibbs@no ha] In my original post i thought i made it clear that i am referring to the
|   |   + 48670 [hal9000@hy e] OK, I'm not flaming you. I'm just trying to communicate.
|   |   + 48680 [ptkwt@sh ll ] All you've said is that the online docs for "modules and methods" was not
|   |   | + 48694 [n1k0@ro er .] A suggestion for the 'ri' program...
|   |   | + 48700 [james@ja es ] If somebody from the "outside" (for lack of a better word) makes a comment
|   |   | | 48703 [botp@de mo t] James, you've said it all (kindly and clearly, too). You have the potential
|   |   | | 48735 [james@ja es ] Thank you.
|   |   | | 48753 [jim@fr ez .o] I recently gave a presentation at work on Ruby
|   |   | | 48756 [james@ja es ] It *is* realistic to expect that every class and module in the standard
|   |   | | + 48768 [jim@fr ez .o] Sounds like the result of my calls to Microsoft support...but I had to pay...
|   |   | | + 48871 [james@ja es ] On a related note, I was wondering if rdtool/rd2 would be returning to the
|   |   | |   48896 [DDouthitt@cu] ...
|   |   | |   48902 [n1k0@ro er .] You're assuming every system in existence (or every system that runs ruby) is
|   |   | |   48906 [meier@me st ] ldoc
|   |   | + 48709 [stibbs@no ha] I personally use Ruby as my main scripting language and feel that the
|   |   | | + 48721 [hal9000@hy e] Sure, I've read it. Thanks for the reply.
|   |   | | + 48731 [ptkwt@sh ll ] Me too :)
|   |   | + 58250 [stibbs@no ha] I personally use Ruby as my main scripting language and feel that Dave's
|   |   + 48707 [list@NO PA c] Specifically stating something general?
|   |   + 58263 [batsman.geo@] TROLL?
|   + 48610 [decoux@mo lo] There is a french expression for this
|     + 48617 [dossy@pa op ] Cool.  Any language that has LART as a real token in the
|     + 48626 [peter@se an ] Those who can do,
|     | 49040 [elderburn@mi] And those who can do neither administrate.
|     | + 49041 [johnknight.c] Ror some the tension of staying in problem space versus jumping into
|     | + 49093 [peter@se an ] The problem I think is that for a Perl or Python shop then Ruby might be
|     |   49131 [elderburn@mi] Agreed. That is sort of what I meant when I noted the move from
|     |   + 49138 [gsinclair@so] [snippage everywhere]
|     |   | + 49149 [james@ja es ] perl -MCPAN -shell
|     |   | + 49150 [dan@si he or] Yup, CPAN.pm, and its shipped with perl for ages.
|     |   | + 49171 [mike@st k. o] Yes,
|     |   + 49147 [peter@se an ] As a for instance today we needed a RTF parse. There it was on CPAN.
|     |     49157 [elderburn@mi] Yes. :-)
|     |     49241 [peter@se an ] See it looks that way to me, maybe I could just convert it into XML and
|     |     49299 [hal9000@hy e] The RTF spec, you mean?
|     |     + 49374 [ jimm@io co ] Not hard at all. There's a header, a footer, font declarations, and
|     |     + 49534 [peter@se an ] The RTF spec from Microsoft looks quite thorough. I can't see any
|     |       + 49574 [pmateescu@no] It is quite easy in fact.
|     |       + 50646 [mrp@cr .c no] a colleague of mine tried to write an RTF parser a few years ago,
|     + 48661 [hal9000@hy e] of
+ 48723 [airboss@no e] I've encountered the same complaints from my co-workers and
| + 48724 [decoux@mo lo] pigeon% rd2 -rrd/rd2man-lib hashlike.rd  | nroff -man | less
| | 48727 [airboss@no e] [...etc...]
| | 48757 [decoux@mo lo] Just use modules which give you documentation, or send a patch to the
| + 48732 [harryo@zi .c] This is just a thought, but, Python has a standard (discussed in this forum
| | + 48738 [n1k0@ro er .] lisp has a similar feature, which emacs uses to produce its documentation
| | + 48749 [yuchingtien@] instead of everyone writing your own documentation, wouldnt a wiki
| |   48750 [mgushee@ha e] I agree with the closing sentence ;-) Wikis are cool, but as the primary
| |   + 48751 [Ephaeton@gm ] You have a pet Triceratops ?! COOL !
| |   + 48770 [list@NO PA c] I believe even a suit can get his head aroun www.emacswiki.org.  So
| + 48923 [comp.lang.ru] - - You haven't been doing Perl very long then. It took YEARS to
|   48930 [james@ja es ] Still, hasn't the Perl experience shown that bundling documentation with the
|   + 48933 [johnknight.c] Unix man pages were/are driven by a standard set of macros. Why not agree
|   + 48980 [list@NO PA c] I'd like rpkg to help in this.  I am designing it around the concept
|   + 48995 [gsinclair@so] Yes!  Yes!  Some Lamarckianism please!  :)
|   | 49006 [hal9000@hy e] But no Lysenkoism... :)
|   + 49017 [comp.lang.ru] - - I think it's a good idea, particularly in a language as
|     + 49021 [mgushee@ha e] And there's always a danger of the embedded documentation getting out of
|     + 49025 [dan@si he or] At 4:25 AM +0900 9/5/02,
|     | 49028 [james@ja es ] So, discussing a problem should not be considered doing something?
|     | + 49029 [DDouthitt@cu] ...
|     | | 49032 [Dave@Pr gm t] Although I agree that wikis are not the best medium for
|     | | 49037 [johnknight.c] I am sorry I did not it make clear that I encourage using wiki as a sort
|     | + 49038 [dan@si he or] Discussing a problem is doing something, but only for the first day
|     + 49026 [john@jo nk i] @   Participants at the beginning were excellent authors as wsel as
|     | 49044 [comp.lang.ru] - - This already exists.
|     | 49057 [james@ja es ] <!-- This first form will search the RDP for a given word or
|     + 49051 [james@ja es ] I don't see people complaining, I see people questioning, or raising
|       49080 [jim@fr ez .o] I have been programming Ruby on a daily basis for
|       + 49082 [johnknight.c] Thanks. rubukitch is very close to what I proposed. I will try and
|       + 49084 [harryo@zi .c] You truly are a brave man :-) !!  Good luck to you, I say.
|       | 49090 [Dave@Pr gm t] This is in the plans for RDoc.
|       | 49091 [harryo@zi .c] I should have guessed :-).
|       | + 49108 [Dave@Pr gm t] Yup - Matz has agreed to let me put RDoc documentation directly in to
|       | + 50308 [jim@fr ez .o] I don't know why, but I must have missed this. It the GTK frontend
|       + 49085 [james@ja es ] I would like to join.
|       + 49087 [gsinclair@so] Great idea.
|       + 49089 [hal9000@hy e] Fine idea. I support it, but I'm too overcommitted
|         + 49099 [jim@fr ez .o] That is fine, but I don't want to overburdern this list.
|         + 49101 [W.L.Kleb@la ] Agreed. How about Ruby Docoumentation Project (RDP), akin to The
|           + 49104 [jim@fr ez .o] rdp sounds good, but it is taken.
|           + 49105 [W.L.Kleb@la ] Oops, I should have written TRDP. http://www.trdp.org/ is registered but
|           | 49107 [djberge@qw s] I've been following the documentation discussion with some interest.  Some
|           | + 49109 [jim@fr ez .o] I personally am not opposed to looking at POD, and I 'personally' don't have
|           | + 49129 [comp.lang.ru] - - Actually this jibes with some thoughts I've had as well. I
|           | + 49136 [james@ja es ] Not a bad idea.  But I imagine the ability to grab a Ruby distribution,
|           |   49141 [gsinclair@so] - relying on Perl installation is not good (as above)
|           |   + 49151 [jim@fr ez .o] I second that.
|           |   | 49211 [matz@ru y- a] OK, I will set up the list soon.
|           |   | 49225 [jim@fr ez .o] Thanks Matz!
|           |   | 49233 [matz@ru y- a] I think it's done.  Try <ruby-doc@ruby-lang.org>.
|           |   | 49236 [W.L.Kleb@la ] Worked for me. I used mailto:ruby-doc-ctl@ruby-lang.org with
|           |   | 49237 [matz@ru y- a] Oops, thank you.
|           |   + 49153 [Dave@Pr gm t] I for one would be very interested in this. What would we want to add
|           |   | + 49167 [jim@fr ez .o] From my perspective, I think that rdoc fits the bill nicely.
|           |   | | 49170 [curt@hi bs c] Since rdoc is already on sourceforge this should be trivial as sourceforge
|           |   | | 49175 [jim@fr ez .o] If ML means mailing list, then I'm not sure that is the place
|           |   | + 49223 [gsinclair@so] Good question.
|           |   + 49172 [mike@st k. o] Does ML mean mailing list or markup language here?
|           + 49134 [james@ja es ] But there is an RDP (Ruby Documentation Project) home page.
+ 48761 [gsinclair@so] This comment is relevant to this thread, but has no particular place it should
  + 48765 [jim@fr ez .o] Try the online pick-axe book.
  | 48771 [gsinclair@so] should
  | + 48773 [decoux@mo lo] Well, there is a problem
  | | 48774 [gsinclair@so] Indeed.  I was looking at my offline backup. :(  It was contained in the
  | + 48797 [jim@fr ez .o] My search found it on page 403 of the pdf version.
  + 48781 [list@NO PA c] The HTML has it in lib_standard.html.
threads.html
top