Skip to main content

Conversion to std::string and return from function

 Many times I have come across code something like the below:

class AClass {


    std::string getName();


std::string AClass::getName() {

    return "I am returning";


Here the member function converts the string constant to std::string while returning. This is in my opinion not necessary. This cast away some flexibility. I mean this way of converting to a std::string while returning to function does not make much sense. 


If we need in any place to get the name as const char* I need to reverse by calling string::c_str()

const char* pName = instanceOfClassA.getName().c_str();

However, keeping the return type as const char* has some benefits:

const char* AClass::getName() const {

    return "I am returning";


1. const char* pName =  instanceOfClassA.getName().getName(); // No Conversion will take place

2. std::string sName = instanceOfClassA.getName().getName(); // Conversion happens to std::string 

So, only based on usage conversion happens. It delays conversion until needed.

Now arguably, we can say that why not use c_str() to get something as const char*. I mean, let the function remain as below: 

std::string AClass::getName() {

    return "I am returning";


The usage may be like this:

const char* pName = instanceOfClassA.getName().c_str(); 

/*Other use of pName.... */

c_str() will return [internal buffer (C++ 11) of std::string as] const char*. But it's not reliable.

Why? The explanation is given in the link

In a line, to simplify it, we can't use data pointed by c_str() past the lifetime of std::string object or changed by a function. In both of those cases, the pointer will be invalidated. 


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,, 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&