#include ;
#include ;

using namespace std;

int main(int argc, char *argv[]){
string s(“This is a basic string.”);
cout << s << endl;
}

Introducing functions that allow programmers to remain ignorant of how their code works might be convenient in the short term, but in the long term the best way to write safe code is understand the language.

C’s strength is that its low level, its not one of these dumbed down flash in the pan convenience languages.

Man, don’t you hate it when you reply too early in the morning?

Little of Googling never hurts. And definitely might have helped to resolve your confusion and avoid silly remark. GNU refused the function for two very simple reasons: (1) there is no stable interfaces/not a POSIX and (2) redundant.

As was pointed many many times, strlcpy() is 100% redundant, as the same effect can be achieved by snprintf(dest,dest_capacity,”%s”,src).

What’s more, snprintf() has very important extra bonus: snprintf(dest,dest_capacity,”%.*s”,src_len,src) which allows to work also on non-zero terminated input.

We could move the historical functions to an , allowing old code to be trivially recompiled if we REALLY don’t want to fix it. Everyone else can use heap storage calculated to fit.

char *strncpy(char *dest, const char *src, size_t n);
char *strncat(char *dest, const char *src, size_t n);

Granted, they don’t return the number of bytes copied in a size_t, but they will only copy ‘n’ number of bytes.