>2018
>doesn't have strings
2018
Matthew Garcia
Henry Hill
>needs strings when you already have arrays of characters
kek
Juan Flores
Char arrays are fine in my book really
Strings are just a sequence of chars anyways
Camden King
>2018
>not a single programming language fast as c
Brandon Williams
citation needed
Wyatt Murphy
needs to end char arrays with '\0'.
Jose Gonzalez
precisely my reaction when I've learned that C++ std::strings need to do that under the hood
Landon Kelly
citation needed x2
Thomas Cox
>t. never worked with unicode
Bentley Rogers
C can do Pascal strings too.
Eli Torres
Only to stay compatible with C, and only when std::string::c_str() is called.
Ryder Jenkins
std::string::c_str() has no side effect and is equivalent to std::string::data() since C++11
Caleb Bell
All strings are char* under the hood
Nathaniel Brooks
All ints are char[4] under the hood.
Andrew Brown
how can it support locales if it doesn't have strings
Benjamin Gonzalez
Wrong. Not every architecture has 32 bit ints.
Noah Parker
But user they do
Ayden Murphy
But C++ has strings
Elijah Peterson
>what is string.h
>what is making your own library
Matthew Reed
>1986
>has strings
>2008
>has generics
>2015
>has namespaces
C can't actually compete with Pascal.
Nathan Price
>what is making your own library
No, no. Just use antirez's sds, motherfucker.
Landon Davis
#include
#define MAXLENGTH 1000
int main(){
char aString = [MAXLENGTH];
return 0;
You now have a string. Enjoy it.