[268] in BarnOwl Developers
Re: Release engineering, packaging and momentum
daemon@ATHENA.MIT.EDU (David Glasser)
Thu Oct 29 18:04:19 2009
Resent-From: nelhage@mit.edu
Resent-To: barnowl-dev-mtg@charon.mit.edu
Date: Tue, 31 Oct 2006 17:02:14 -0500
From: "David Glasser" <glasser@MIT.EDU>
To: "Sam Hartman" <hartmans@mit.edu>
Cc: "Nelson Elhage" <nelhage@mit.edu>, dirty-owl-hackers@mit.edu
In-Reply-To: <tslmz7cry4x.fsf@cz.mit.edu>
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?
I think this can be solved with standard Perl "exporter" techniques.
--dave
--
David Glasser | glasser@mit.edu | http://www.davidglasser.net/
