[3171] in BarnOwl Developers
[barnowl/barnowl] b9517c: Explicitly store whether an owl_message has a ZNot...
daemon@ATHENA.MIT.EDU (noreply@github.com)
Wed Jul 27 02:39:01 2011
Date: Tue, 26 Jul 2011 23:38:57 -0700
To: barnowl-dev@mit.edu
From: noreply@github.com
Branch: refs/heads/master
Home: https://github.com/barnowl/barnowl
Commit: b9517cf7ce2959a6e86a52d25a98b1d03df56d58
https://github.com/barnowl/barnowl/commit/b9517cf7ce2959a6e86a52d25a98b1d03df56d58
Author: David Benjamin <davidben@mit.edu>
Date: 2011-07-24 (Sun, 24 Jul 2011)
Changed paths:
M functions.c
M message.c
M owl.h
M perlconfig.c
Log Message:
-----------
Explicitly store whether an owl_message has a ZNotice_t
We should remove it altogether in perlmessages, but in the meantime, we
shouldn't be crashing on faked incoming zephyr messages. Also drop the
attempted fake ZNotice_t in owl_perlconfig_hashref2message. No one could
have relied on it safely today because any such message would crash on
delete.
Commit: a74a04441b9bb3d375840a9198cd9c529be66f9f
https://github.com/barnowl/barnowl/commit/a74a04441b9bb3d375840a9198cd9c529be66f9f
Author: David Benjamin <davidben@mit.edu>
Date: 2011-07-24 (Sun, 24 Jul 2011)
Changed paths:
M tester.c
Log Message:
-----------
Free the owl_message created for testing
It's safe to do so now.
Compare: https://github.com/barnowl/barnowl/compare/f271129...a74a044
