Return std::string instead of dynamic allocations
We mostly use classical C strings, but the memory management around them can get confusing and error prone. Let's use std::string for the cases where we need to return a newly allocated string.
Showing
- common/network/TcpSocket.cxx 14 additions, 7 deletionscommon/network/TcpSocket.cxx
- common/network/TcpSocket.h 3 additions, 2 deletionscommon/network/TcpSocket.h
- common/rfb/CConnection.cxx 8 additions, 7 deletionscommon/rfb/CConnection.cxx
- common/rfb/CMsgHandler.cxx 1 addition, 4 deletionscommon/rfb/CMsgHandler.cxx
- common/rfb/CMsgReader.cxx 2 additions, 2 deletionscommon/rfb/CMsgReader.cxx
- common/rfb/CSecurityDH.cxx 8 additions, 9 deletionscommon/rfb/CSecurityDH.cxx
- common/rfb/CSecurityMSLogonII.cxx 8 additions, 9 deletionscommon/rfb/CSecurityMSLogonII.cxx
- common/rfb/CSecurityPlain.cxx 7 additions, 8 deletionscommon/rfb/CSecurityPlain.cxx
- common/rfb/CSecurityRSAAES.cxx 15 additions, 18 deletionscommon/rfb/CSecurityRSAAES.cxx
- common/rfb/CSecurityVncAuth.cxx 4 additions, 6 deletionscommon/rfb/CSecurityVncAuth.cxx
- common/rfb/ComparingUpdateTracker.cxx 3 additions, 5 deletionscommon/rfb/ComparingUpdateTracker.cxx
- common/rfb/Configuration.cxx 21 additions, 25 deletionscommon/rfb/Configuration.cxx
- common/rfb/Configuration.h 12 additions, 16 deletionscommon/rfb/Configuration.h
- common/rfb/DecodeManager.cxx 9 additions, 12 deletionscommon/rfb/DecodeManager.cxx
- common/rfb/EncodeManager.cxx 13 additions, 17 deletionscommon/rfb/EncodeManager.cxx
- common/rfb/Hostname.h 6 additions, 9 deletionscommon/rfb/Hostname.h
- common/rfb/LogWriter.cxx 1 addition, 1 deletioncommon/rfb/LogWriter.cxx
- common/rfb/SConnection.cxx 8 additions, 7 deletionscommon/rfb/SConnection.cxx
- common/rfb/SMsgHandler.cxx 1 addition, 4 deletionscommon/rfb/SMsgHandler.cxx
- common/rfb/SMsgReader.cxx 2 additions, 2 deletionscommon/rfb/SMsgReader.cxx
Loading
Please register or sign in to comment