From 2bf5cc0f588793051817b6189c1f68635a03fcae Mon Sep 17 00:00:00 2001 From: JoeArizona Date: Mon, 6 Mar 2017 08:41:29 -0700 Subject: [PATCH] Fixed several broken links MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Hi Paul – Most of your links are broken – in many cases the websites as such don't even exist anymore. I found good replacement links for safestr, fireString, wxString, etc. (I couldn't find anything on "Str Library", which is probably a tough name to search.) Note that many of your comparisons are against libraries that were abandoned 14 or more years ago (e.g. fireString and libclc were abandoned in 2003). I for one would love to read updated comparisons with modern, active libraries – string handling is fundamentally important. --- bstrlib.txt | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/bstrlib.txt b/bstrlib.txt index 26fc927..1985600 100644 --- a/bstrlib.txt +++ b/bstrlib.txt @@ -3231,7 +3231,7 @@ wxString class This is the string class used in the wxWindows project. A description of wxString can be found here: -http://www.wxwindows.org/manuals/2.4.2/wx368.htm#wxstring +https://wiki.wxwidgets.org/WxString This C++ library is similar to CBString. However, it is littered with trivial functions (IsAscii, UpperCase, RemoveLast etc.) @@ -3396,7 +3396,7 @@ The goals of libclc and Bstrlib are clearly quite different. fireString ---------- -http://firestuff.org/ +ftp://ftp.irisa.fr/pub/mirrors/gnu/www.gnu.org/directory/all/FireString.html 1. Uses standard char * buffer, and adopts C 99's usage of "restrict" to pass the responsibility to guard against aliasing to the programmer. @@ -3413,7 +3413,7 @@ Safe C String Library A library written for the purpose of increasing safety and power to C's string handling capabilities. -http://www.zork.org/safestr/safestr.html +https://www.securecoding.cert.org/confluence/pages/viewpage.action?pageId=5111861 1. While the safestr_* functions are safe in of themselves, interoperating with char * string has dangerous unsafe modes of operation. @@ -3460,6 +3460,7 @@ modified and yet where a fixed sized buffer is undesirable.) Libsrt ------ +https://github.com/faragon/libsrt This is a length based string library based on a slightly different strategy. The string contents are appended to the end of the header directly so strings only require a single allocation. However, whenever a reallocation occurs, @@ -3477,7 +3478,8 @@ dedicate an expert to learn the internals of the library). SDS --- -Sds uses a strategy very similar to Libsrt. However, it uses some dynamic +https://github.com/antirez/sds +SDS uses a strategy very similar to Libsrt. However, it uses some dynamic headers to decrease the overhead for very small strings. This requires an extra switch statement for access to each string attribute. The source code appears to use gcc/clang extensions, and thus it is not portable.