Per Hedbor () @ Pike (-) developers forum wrote:
Personally I think it could be removed entirely. It's not like it's all that common for people to try to decode .o-files generated by other versions of pike at all.
Quite. Simply checkout an old version of Pike, and decode with that.
Speaking about encode: How about putting the encode code for programs in a separate .so file, that is only loaded when dumping programs?
Sounds very good. Would help the embedded Pike solution a lot.
function to make the decode_value function smaller (usually gcc generates better code for small functions. Usually.)
Have you checked/noticed this? It shouldn't matter, actually. Last time I checked the innards of gcc was around 1996, so my data is a bit dated, but back then it didn't matter. The lifetime analysis for local variables of gcc is quite good (provided you don't use pointers). When you use lots of pointers, it gets a bit hairy though.