[245] in BarnOwl Developers
Re: [D-O-H] r419 - trunk/owl
daemon@ATHENA.MIT.EDU (Alejandro R. Sedeno)
Thu Oct 29 18:04:04 2009
Resent-From: nelhage@mit.edu
Resent-To: barnowl-dev-mtg@charon.mit.edu
Date: Tue, 31 Oct 2006 18:49:59 -0500
From: "Alejandro R. Sedeno" <asedeno@MIT.EDU>
Reply-To: dirty-owl-hackers@MIT.EDU
To: dirty-owl-hackers@mit.edu
In-Reply-To: <tsl3b94rwtl.fsf@cz.mit.edu>
Sam Hartman wrote:
> Why do we want owl_message_type_jabber visible in the C sources?
>
> --Sam
OWL_MESSAGE_TYPE_JABBER is in the C code because kretch put it there.
owl_message_is_type_jabber() exists because I felt it was wrong to have
owl_message_is_type_foo() for only a subset of FOOs defined in owl.h.
Currently, owl expects messages to have a type and I figured it would be
clever to have jabber messages be of the existing type
OWL_MESSAGE_TYPE_JABBER. I've also thought that having an
OWL_MESSAGE_TYPE_EXTERNAL might be interesting, and that we could check
for it and make calls out to perl for lots of things based on it. I went
with using the internal type initially because the idea came to me first.
-Alejandro
