It looks from the headers that Module::step is deprecated in 1.0. But my plugins still use step and build without deprecation warnings. How is this possible?
process calls step by default.
But should we treat step as deprecated? Or for now is step a fully supported subset of process?
tx in advance. 1.0 is really nice.
Yes, step is deprecated.
I’ll get rid of it then. strange that it doesn’t cause gcc to give me a deprecated warning. I try to keep those at zero. thanks.
Overriding a function marked deprecated does not give a warning in GCC and Clang.
1 Like