Most of my career before retirement was spent in the security industry developing hardware and software for detection of intruder and fire hazards,Īnd rapid communication to either on-site or remote security guards of any intruders or fires etc.Īny spurious alarm could initiate the despatch of Armed Guards at a military installation, I would guess that Piriform has a battery of tests that they perform to reduce the chance of issuing software that can damage the user's software installation or documents.
Yes, that was extremely bad software development and we all know better now - or do we, or Microsoft, or Apple If the binary code has changed then the actions will change, and without access to the source code it would be difficult to predict which actions will change.Ībout 30 years ago I came across an incident where the Version String was not only used to show the version and date of creation,īut had also been depended upon as a data string that governed the actions of a subroutine, and when another developer updated the software it crashed.Īfter reversion tests he found that the version string was critical BUT the original coder had not documented that a function depended upon its data value. Has anyone performed hash-checksum comparisons between the Beta and the Final Production binaries of the OS 10.9. You may well be perfectly correct about how to fix the problem. Piriform just needs to change the version check from 10.8 to 10.9 in there app and the ccleaner program will work.
0 kommentar(er)
