My point was that, you could design it in a way such that you do not have to resort to macros....moc...or whatever that changes the source.
AFAI see, that is done in the library discussed...
Type: Posts; User: manasij7479
My point was that, you could design it in a way such that you do not have to resort to macros....moc...or whatever that changes the source.
AFAI see, that is done in the library discussed...
Right.. :(
But a device is also, logically a function; (...here, also having a state-machine as the back-end)
You give a computer some inputs, (interactively or not)...and it produces an unique output...that...
It would have different functions...as a computer does.
The () operator just represents the action : 'powering on'.
That is only one kind of use for them.
For example...if you have a class called Computer....its () operator could be appropriately used to start the computer ...
That doesn't mean that the objects...
...but a functor IS an object !
I read that their explanation is "using callbacks overrides the type system for the arguments."
But I never understood that point...if you use functors instead of function pointers as expected in...
I think, from the examples, the keyword is 'simple' .