Only in the most limited sense of "deprecated", and for reasons unrelated to line endings.
The original use case for those functions was to convert a character to an ASCII value or vice versa. Fine for the first couple decades of personal computing, but of course useless in the modern Unicode world.
For those who had been relying on them to derive integer values from a single byte, v7 and forward include byteToNum and numToByte.
For those wanting to know the numeric value of a character within Unicode, we now have codePointToNum and numToCodePoint.
And for the subset of people working with ASCII data, charToNum and numToChar continue to work, and AFAIK there's no plan to remove them. Scripters are merely cautioned against using them for the same scope of use cases they were originally created for, since Unicode has required the engine team to add those new alternatives which will usually do a more reliable job with modern encodings.