From: John Conrad <john.emerson.conrad@...>
Date: 2006-05-11T08:55:50+09:00
Subject: Re: Ruby documentation discovery

------=_Part_74326_2514205.1147305341870
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On 5/10/06, benjohn@fysh.org <benjohn@fysh.org> wrote:
>
> *snip*
>
> > I saw some code that said "require callbacks". I saw that it referenced
> > a
> > Callback class. So I went to the terminal and typed ri Callback, but ri
> > said
> > nothing was known about Callback.
>
> I believe your post is about documentation, rather than callbacks.
> However: a "callback" is a general term. It's a function / method that
> you register with some entity, so that when that entity encounters a
> particular type of event, it will call the registered function.
>

Callback might not have been the best example for me to use; it just
happened to be the most recent experience. I knew what a callback function
does, generally speaking, but when I saw the line "require 'callbacks'", I
started to suspect that perhaps ruby has some sort of "official" callback
library that I ought to be aware of. It turns out that xmpp4r has its own
little callbacks library which I didn't notice at first because the
callbacks.rb file gets installed separately from the rest of the xmpp4r
files. (Not sure why.)

------=_Part_74326_2514205.1147305341870--