> I'm not convinced "straightforward" is quite the right word.
I should have been more specific. I'm referring only to DB_LINK. For CA_LINK and beyond, it is not so straightforward.
> ... making use of the db_access vs dbAccess split.
oh, evil. I can see some potential problems, mainly how to deal with "#include <epicsTime.h>" in two contexts.
> We'd have to be careful with the C++ One Definition rule
Practically, I don't think this is an issue. There is no usage of RTTI.
> I'm not convinced "straightforward" is quite the right word.
I should have been more specific. I'm referring only to DB_LINK. For CA_LINK and beyond, it is not so straightforward.
> ... making use of the db_access vs dbAccess split.
oh, evil. I can see some potential problems, mainly how to deal with
"#include <epicsTime.h>" in two contexts.
> We'd have to be careful with the C++ One Definition rule
Practically, I don't think this is an issue. There is no usage of RTTI.