[erlang-questions] Strings - deprecated functions

[Anthony Ramine]

I don't particularly care about the old functions myself (if you want to run old code, just run a damn old VM, problem solved), but a way to reorganise the documentation to accommodate for that would also bring closure to  https://github.com/erlang/otp/pull/363, which would be nice.

> Le 27 nov. 2017 à 03:03, Robert Virding <rvirding@REDACTED> a écrit :
> 
> I think it is perfectly possible to keep the old functions in the same 'string' module in a clean way if you just reorganise the documentation. Now all the functions, both the new and the obsolete, are kept in one alphabetical list which makes it difficult to see which are which and get a clear overview of the functions. Why not just separate the functions into 2 groups, the new and the obsolete, each in its own alphabetical list? This would make it easy to keep the old functions while making it easy for people to choose the newer ones, and migrate code if desired. There would then be no need to get rid of the old functions and break backward compatibility.