Skip to main content

Bind lambda with a class and execute while class instance destroys (A final pattern)

 Let's have a template class like below:

template< typename T >
class finalGuard {
    T m_func;
public:
    finalGuard(T func) : m_func(func) {}
    ~finalGuard() { m_func(); }
};

What is the requirement? I need to execute lambda when a template instance of the above class goes out of scope or any exception is caused during the execution of code. We can think of this as more or like a final pattern. When a class object's lifetime ends, a piece of code will start executing to wrap up things. 

Now I have a factory-like function defined as below to resolve type dependency which lambda is expecting:

template< typename T >
finalGuard< T > finalCall(T obj) { return obj; } 

The below piece of code is used to bind the lambda with the class instance and it gets executed as soon as a class object destructor gets invoked.

int main()
{
    try {
        auto guard = finalCall([]() noexcept {
            cout << "Good bye via exception!\n";
            });
        cout << "This is followed by a throw statement\n";
        throw runtime_error("Unknown Error"); // This is a throw which calls finalCall 
        cout << "This line will never execute\n";
    }
    catch (exception& ex) { cout << "This is caused by an " << ex.what() << "\n\n"; }

    {
        auto guard = finalCall([]() noexcept {
            cout << "Good bye via normal execution!\n";
            });
        cout << "This is a simple execution\n";
        cout << "Normal execution ends here...\n"; 
    }

    return 0;
}

So, as mentioned above code, irrespective of the execution path lambda will be executed to do some work.

The above code works with Microsoft VS 2019, and GNU C++ [C++ 11/14/17].

If we are targeting only the GNU C++ compiler then code can be stripped down a bit. In that case, we don't need a factory-like function explicitly. (Used GCC 11.1.0) 

#include <iostream>
#include <stdexcept>

using std::cout;
using std::exception;
using std::runtime_error;

template< typename T >
class finalGuard {
    T m_func;
public:
    finalGuard(T func) : m_func(func) {}
    ~finalGuard() { m_func(); }
};

/*
Resolving type dependency for lambda is not needed on GCC C++ 17 onwards.
//template< typename T >
//finalGuard< T > finalCall(T obj) { return obj; }
*/ 

int main()
{
    try {
        auto guard = finalGuard([]() noexcept {
            cout << "Good bye via exception!\n";
            });
        cout << "This is followed by a throw statement\n";
        throw runtime_error("Unknown Error"); // This is a throw which calls finalCall 
        cout << "This line will never execute\n";
    }
    catch (const exception& ex) { cout << "This is caused by an " << ex.what() << "\n\n"; }

    {
        auto guard = finalGuard([]() noexcept {
            cout << "Goodbye via normal execution!\n";
            });
        cout << "This is a simple execution\n";
        cout << "Normal execution ends here...\n"; 
    }

    return 0;
}


Comments

Popular posts from this blog

Variadic template class to add numbers recursively during compilation

 The idea of having a class to add numbers (variable parameters) during compilation time recursively. Also wanted to restrict types to a single type while sending parameters to class member function. That said, if we mix int, float and double types to add function shall result in compilation error. How do we achieve this. The below is the code which actually helps to achieve this: <code> #include < fmt/format.h > template < typename T> class MyVarSumClass{     private :         T _sum = 0 ;     public :         template < typename ... TRest>         T add(T num, TRest... nums){             static_assert (std::conjunction<std::is_same<TRest, T>...>{}); /* Assert fails                if types are different */             _sum += num;             return add(nums...); // Next parameter packs gets picked recursively         }         // Base case         T add(T num){             _sum += num;             return _sum;         } }; int main() {     My

A simple approach to generate Fibonacci series via multi-threading

T his is a very simple approach taken to generate the Fibonacci series through multithreading. Here instead of a function, used a function object. The code is very simple and self-explanatory.  #include <iostream> #include <mutex> #include <thread> class Fib { public:     Fib() : _num0(1), _num1(1) {}     unsigned long operator()(); private:     unsigned long _num0, _num1;     std::mutex mu; }; unsigned long Fib::operator()() {     mu.lock(); // critical section, exclusive access to the below code by locking the mutex     unsigned long  temp = _num0;     _num0 = _num1;     _num1 = temp + _num0;     mu.unlock();     return temp; } int main() {     Fib f;          int i = 0;     unsigned long res = 0, res2= 0, res3 = 0;     std::cout << "Fibonacci series: ";     while (i <= 15) {         std::thread t1([&] { res = f(); }); // Capturing result to respective variable via lambda         std::thread t2([&] { res2 = f(); });         std::thread t3(

A concept to a product (Kimidori [ 黄緑]) - Part 2

In the previous part , we have seen KIMIDORI [ 黄緑] detect if a URL is malicious. In this part, we will see the details that KIMIDORI [ 黄緑] fetches out of the URL provided. As an example, provided a safe URL, https://www.azuresys.com/, and let's see what it brings out: As we can see, the link is safe and the link is active, which means we can just click on the link to open it on IE.  Now it's time to look into the URL report (still under development):  We have URLs IP, Location, and HTTP Status code. The Report part is a sliding window, the Show Report button shows as well as hides the report. Show / Hide Report is a toggle button. Let's see if we get the same details for any bad (phishing / malicious) URL: Took an URL example from a phishing link and tested it. The tool detected it as not a good link (Screen Shot Below) & link does not activate unlike a safe URL: Now let's see the report part for more details including domain registration details: It looks like it&