issue 2
(Naming conflict with database_error::assert) reported by goo...@mani.de
- I tried to compile hiberlite on Mac OS X, but it failed on database_error::assert, because in Debug-
builds a preprocessor-macro named "assert" is defined.
I replaced database_error::assert with database_error::database_assert and then it compiled fine.
I tried to compile hiberlite on Mac OS X, but it failed on database_error::assert, because in Debug-
builds a preprocessor-macro named "assert" is defined.
I replaced database_error::assert with database_error::database_assert and then it compiled fine.
Older
Aug 05, 2008
issue 1
(Non-intrusive hibernation) reported by austin.bingham
- I was wondering how complete the support for non-intrusive hibernate
functions are. I noticed that you have hibernate functionality for some stl
containers, so clearly you have some support for hibernating classes that
you don't own. Is this generally safe to do for any class?
In particular, I would like to be able to hibernate classes generated from
protocol buffer definitions.
Sorry for posting this to "open issues" since it's really more of a
question. Perhaps a wiki page describing this functionality would be good.
I was wondering how complete the support for non-intrusive hibernate
functions are. I noticed that you have hibernate functionality for some stl
containers, so clearly you have some support for hibernating classes that
you don't own. Is this generally safe to do for any class?
In particular, I would like to be able to hibernate classes generated from
protocol buffer definitions.
Sorry for posting this to "open issues" since it's really more of a
question. Perhaps a wiki page describing this functionality would be good.
