Your class would need to have methods to update its parameters, don’t call the constructor again or you get a new instance
This would be the brute force way
Flasher instance1(1, 2, 3);
...
instance1.~Flasher(); // destructor
new(&instance1) Flasher(4, 5, 6); // reconstruct
...
// Final destruction is be done automatically
This would be better in my opinion If part of your class intended behavior is to be initialized several times. The constructor of your class can simply use a public configuration method, something like
class Flasher {
public:
Flasher(int a, int b, int c) {
configure(a,b,c);
}
void configure(int a, int b, int c) { ... }
};
then you can call the method configure yourself what you want to update the settings
I think OP removed her/his class code to keep the post short and is trying to re-initialize an instance by calling the constructor... may be I got that wrong