[269] in BarnOwl Developers
Re: Release engineering, packaging and momentum
daemon@ATHENA.MIT.EDU (Sam Hartman)
Thu Oct 29 18:04:21 2009
Resent-From: nelhage@mit.edu
Resent-To: barnowl-dev-mtg@charon.mit.edu
From: Sam Hartman <hartmans@MIT.EDU>
To: "David Glasser" <glasser@mit.edu>
Cc: "Nelson Elhage" <nelhage@mit.edu>, dirty-owl-hackers@mit.edu
Date: Tue, 31 Oct 2006 19:37:50 -0500
In-Reply-To: <1ea387f60610311402x22c4248fje9a33e5266c4b475@mail.gmail.com>
(David Glasser's message of "Tue, 31 Oct 2006 17:02:14 -0500")
>>>>> "David" == David Glasser <glasser@MIT.EDU> writes:
David> On 10/31/06, Sam Hartman <hartmans@mit.edu> wrote:
>> Hmm. Do you really want code owl calls to implement the module
>> interface--which I guess really means code owl loads that calls
>> new_command and links into the hooks. to be in the same
>> namespace as code that you use as libraries.
>>
>> I.E. is the part of ColorUtils that jabber wants to use really
>> belong in the same package/namespace as the part that sets up
>> commands and puts itself in the message reception loop?
David> I think this can be solved with standard Perl "exporter"
David> techniques.
How? I understand Exporter, but I don't understand how it addresses
when to add yourself to various hooks.
