Well, I merely tied up the loose ends that were a natural result of all compat support prior to 7.8 being ripped out already (not by me). I.e. the functionality that *I* removed was already dead-in-the-water because there was no way to call it anymore.
No, you could still call them. I kept them in because just because it was compatibility with old data, not old code.
Martin Nilsson (Opera Mini - AFK!) @ Pike (-) developers forum wrote:
Well, I merely tied up the loose ends that were a natural result of all compat support prior to 7.8 being ripped out already (not by me). I.e. the functionality that *I* removed was already dead-in-the-water because there was no way to call it anymore.
No, you could still call them. I kept them in because just because it was compatibility with old data, not old code.
Ok, misjudgement from my side then. Are there really permanently stored datastructures that need to be accessed using those old hash functions from Pike 8.2 and beyond? I personally never store hashes in files, I thought they were only/mostly used for in memory datastructures.
Martin Nilsson (Opera Mini - AFK!) @ Pike (-) developers forum wrote:
No, you could still call them. I kept them in because just because it was compatibility with old data, not old code.
Ok, misjudgement from my side then. Are there really permanently stored datastructures that need to be accessed using those old hash functions from Pike 8.2 and beyond?
Stored data is unlikely, there are however old Pike-based RPC-style implementations that expose the hash value in the binary protocol.
pike-devel@lists.lysator.liu.se
-
Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum -
Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum
-
Stephen R. van den Berg