[1464] in BarnOwl Developers
Reorganizing perlwrap.pm
daemon@ATHENA.MIT.EDU (Nelson Elhage)
Thu Oct 29 18:16:55 2009
Resent-From: nelhage@mit.edu
Resent-To: barnowl-dev-mtg@charon.mit.edu
X-Original-To: nelhage@lunatique.mit.edu
Date: Fri, 22 May 2009 19:18:30 -0400
From: Nelson Elhage <nelhage@MIT.EDU>
To: barnowl-dev@mit.edu
I'm getting annoyed at the huge perlwrap.pm file. I'd like to find a
solution that lets us split the modules out into their own .pm files.
In particular, I think I want to split it out into perl/lib/BarnOwl/*,
and then stop linking in any perl code, and instead just do a 'use
BarnOwl' on startup. In order to make this work, we would have barnowl
somehow detect if it was running out of a build dir, and set its share
directory to "$builddir/perl/", instead of the default compiled-in
location.
The current motivation for perlwrap.pm is that by linking it into the
binary, we ensure that a barnowl has enough perl statically linked in
in order to be useful even without its share directory. Personally,
I'm not really concerned about that, and am willing to break that
property.
However, I want to ask other peoples' opinions, and see if anyone
objects to this plan, or has a better proposal.
- Nelson
