ESP8266 Community Forum

- Tue Mar 22, 2016 4:13 pm #43823 in the previous versions <2.0 this library command would return *char,
Now for some reason it returns
String
the object type.
to me this is bad, is it intentional and is it going to stay?
I have a little function I was using to connect the wifi to the strongest access point that I have the password for.
Its broken now and to fix it I need to read this value as a string and then convert it to a const char* I believe to plug it into WiFi.begin(ssid)

Or am I doing something wrong?

- Tue Mar 22, 2016 4:44 pm #43826 Why not simply do a WiFi.SSID().c_str() ?

- Tue Mar 22, 2016 5:39 pm #43828 sure I can convert it,
but I was under the impression (and please correct me if I'm wrong) that using the String object results in a 2K overhead.
I have learnt to avoid them like the plague, even though they do often provide a much simpler and more elegant way of dealing with Ascii type characters. With my level of programming knowledge I struggle with c_strings and look up functions from the standard library that I am not all familiar with in order to avoid the String object.

- Tue Mar 22, 2016 6:14 pm #43829 No, there is no such thing about 2K overhead. I don't know where you got this impression.