should really deal with errno=EINTR due to signal, and errno=ETIMEDOUT appropriately.
should really deal with errno=EINTR due to signal, and errno=ETIMEDOUT appropriately.
: add a bool setPeriod(double) function to allow changing the period at run-time.
: add a bool setPeriod(double) function to allow changing the period at run-time.
: add a bool setPeriod(double) function to allow changing the period at run-time.
might be improved by using equal_range
might be improved by using equal_range
: shouldn't this belong in the template type info ? This allows the type lib to choose which locked/lockfree algorithms are implemented and leaves out 4x code generation for each alternative in each compilation unit. Contra: needs T in typelib.
: since setDataSample, initial_value is no longer needed.
: shouldn't this belong in the template type info ? This allows the type lib to choose which locked/lockfree algorithms are implemented and leaves out 4x code generation for each alternative in each compilation unit. Contra: needs T in typelib.
: since setDataSample, initial_value is no longer needed.
This class can be refactored into a base class with generic mqueue code and a subclass with type specific info.
This is an inspiration for a generic, transport independent channel element.
This class can be refactored into a base class with generic mqueue code and a subclass with type specific info.
This is an inspiration for a generic, transport independent channel element.
TODO there is no streambuf and string is used, maybe a streamsbuf might be better, for encapsulating buffering policies (like BS meant it of course). Another todo is to have at least the save get and put/write functions as in istream and ostream. Thanks to the GCC 3.X cleanup, we might be able to mimic quite a lot.
TODO there is no streambuf and string is used, maybe a streamsbuf might be better, for encapsulating buffering policies (like BS meant it of course). Another todo is to have at least the save get and put/write functions as in istream and ostream. Thanks to the GCC 3.X cleanup, we might be able to mimic quite a lot.
check the identifier parser implementation of asserting when a keyword is wrongly used as an identifier. In current implementation it almost never throws.
check the identifier parser implementation of asserting when a keyword is wrongly used as an identifier. In current implementation it almost never throws.
This class is a light-weight implementation of a internal::DataSource<bool>. It may be profitable to remove this low level class and replace its use by internal::DataSource<bool>. That would also cause the removal of most Condition* classes.
This class is a light-weight implementation of a internal::DataSource<bool>. It may be profitable to remove this low level class and replace its use by internal::DataSource<bool>. That would also cause the removal of most Condition* classes.
check why lexeme_d[] is used in implementation, thus why datacalls are parsed on the character level instead of on the phrase level. (probably for the dots ?)
check why lexeme_d[] is used in implementation, thus why datacalls are parsed on the character level instead of on the phrase level. (probably for the dots ?)
Implement the whole transition mechanism with the Strategy software pattern to allow cleaner implementation.
Implement the whole transition mechanism with the Strategy software pattern to allow cleaner implementation.
The ValueChangeParser.cxx implementation needs refactoring.
The ValueChangeParser.cxx implementation needs refactoring.
