Is this a radical change? Probably not.
A radical change to me is something that is someone coming in and removing virtually everything from the post and reposting their own answer in their own words. (It's similar to vandalism, except a vandalized post usually doesn't attempt to provide a new answer, it usually just adds nonsense or unnecessary commentary). Like everything else, it is subject to your own interpretation.
My interpretation of "Radical Change" does probably fall on the extreme side of the spectrum. But a more liberal interpretation would probably be something that changes the answer, rather than fixing a small typo. This itself can be a gray area as a minor edit could make a significant change to the answer, so you sometimes have to make your own call as to if it is "Radical" or not.
It also sounds like you were asking how you should handle this. In general, editing code in answers to change the context of an answer is a big gray/grey area. There are 2 schools of thought:
- Do not change an answer. You should only edit to fix code markup and grammar mistakes;
- If the code is wrong, and especially if it is an accepted answer, it needs fixed so we are not promoting incorrect answers on the site.
I don't think either extreme is always correct as it depends on the situation and your own knowledge of the technologies involved.
When I am reviewing an edit that is changing code in an answer or changing wording that would change the context of the answer i always ask myself:
- Am I familiar with the language and the concepts in the question and the answer?
- If so, is the original code actually wrong?
- And if it is wrong is the edit accurate?
If it meets all 3 criteria, then go ahead and approve. If it fails any of the 3 tests, then I usually reject or skip.
If it fails #1 and if the editor provides a solid reason in the comment for making the edit, then I'll usually skip and let someone who is more versed to judge the technical merits of the question.
If it fails #2 or #3, then I'll usually reject as an "Invalid Edit".
In the edit you referenced, I do not see it as extreme so I definately would not have called it a "Radical Edit", and I probably would have skipped it since my RegEx is rusty and it would have taken me too long to actually determine if the edit is correct or not, and if it needed changed to begin with. I would not have rejected though in this case because it was the OP of the question that actually made the edit and my logic would have been that the OP tried it, saw it was close but didn't quite work for him, and it needed tweaked slightly.
However, if I was versed enough to approve it, I probably would have selected Improve instead and removed the "EDIT" section that was added. The revision history should be enough that you don't need to put an edit header for every little change.