[#2320] Problems in mathn, rational, complex, matrix — Gavin Sinclair <gsinclair@...>
I received a message from Richard Graham mentioning a problem in the
[#2346] Patch for socket.c: control reverse lookup for every instance — Thomas Uehlinger <uehli@...>
Hi all
[#2357] Use the BasicSocket#do_not_reverse_lookup flag in Webrick — Thomas Uehlinger <uehli@...>
Hi
[#2367] Standard libraries — Dave Thomas <dave@...>
From ruby-dev summary:
Hi,
Hi,
By the way, this issue is about a matter of taste, so the debate is somewhat
Hi,
On Thu, Feb 12, 2004 at 02:58:22PM +0900, NAKAMURA, Hiroshi wrote:
On Thursday, February 12, 2004, 8:18:32 PM, Mauricio wrote:
On Thursday 12 February 2004 04:37, Gavin Sinclair wrote:
On Friday, February 13, 2004, 12:44:15 AM, Sean wrote:
(Dave Thomas: there's a question for you in the second paragraph; if you're
[#2397] PATCH: deprecate cgi-lib, getopts, importenv, parsearg from standard library — Gavin Sinclair <gsinclair@...>
Index: cgi-lib.rb
* Gavin Sinclair (gsinclair@soyabean.com.au) wrote:
On Thursday, February 12, 2004, 11:39:37 PM, E wrote:
Hi,
Hi,
[#2422] Re: [ruby-cvs] ruby: * lib/ftools.rb: documented — "U.Nakamura" <usa@...>
Hello,
[#2449] make install not getting through rdoc phase — "David A. Black" <dblack@...>
Hi --
[#2465] PATCH: OpenStruct#initialize to yield self — Gavin Sinclair <gsinclair@...>
This is a common approach I use to object initialization; I don't know
On Fri, 20 Feb 2004 02:42:00 +0900, Dave Thomas wrote:
> > As more general suggestion. Could 'new' yield the new object is a block
On Fri, 20 Feb 2004 08:24:31 +0900, Carlos wrote:
Hi,
Yukihiro Matsumoto wrote:
On Feb 20, 2004, at 4:33 PM, Joel VanderWerf wrote:
[#2494] rehash segfault — Nathaniel Talbott <nathaniel@...>
I don't have a lot of information on this bug at this point, but
Hi,
On Wed, Feb 25, 2004 at 03:30:54AM +0900, Yukihiro Matsumoto wrote:
[#2504] foldl and foldr — "Sean E. Russell" <ser@...>
Sorry if I'm opening old wounds; I have a hard time believing that nobody has
Re: Intelligent eyes needed
Hi --
On Sun, 29 Feb 2004, Dave Thomas wrote:
> I'm in the middle of updating the Pickaxe, and I wanted to try to
> explain better the differences between proc, Proc.new, and blocks. I
> also wanted to explain how break, next, and return work with blocks and
> procs.
>
> I've come up with
> http://www.pragmaticprogrammer.com/extracts/blocks.pdf as my first pass
> at an explanation. If folks have time, I'd really appreciate comments,
> both on the accuracy (Matz?) and on how clear it is. Is the explanation
> correct? Is it as simple as possible? Have I covered all the cases?
>
> This stuff is in the language reference section of the PickAxe, and so
> is supposed to be a little bit terse.
(It may just be my eyes, but I think I see my last name in the first
sentence of "Return and Blocks" :-)
Possible useful tidbit: At RubyConf 2003, Matz agreed that it was a
good idea to get rid of 'proc', in favor of the exclusive use of
'lambda'. The argument for this is that it's confusing to have "proc
{}" and "Proc.new {}" behave differently.
You've gotten around this, in a sense, with the concept of "iterator
context" and "closure context". But I still hope "proc" goes away...
and if it's going to, that might be something you'd want to mention.
My general reaction is that what you've written is very thorough and
clear, and that it reminds me of how much I don't like the direction
Procs and blocks are going :-( But that's for another thread.
David
--
David A. Black
dblack@wobblini.net