I've recently noticed a disturbing behavior of the code formatting shortcut (Ctrl + K) that seems to be completely invalid. It appears that applying Ctrl + K resulted in content change (which was correct logically, but completely defaced the question being asked). Here is the question on SO: Heap corruption using calloc . Initially I assumed the edit in revision 3 was incorrect and rolled it back. Later I edited myself by applying Ctrl + K and got the same result and had to change it back manually to the original code.
That's not the indentation by CTRL-K doing that. It's part of the
* asterisks in the code being interpreted as italics when the code is not indented.
When looking at a strange change in a post, always look at both methods of displaying the difference; if you look at the change in markdown only spaces have been added.
The code really does use
float ** and
sizeof(float*) but that wasn't visibile before adding proper indentation:
PermLaster= (float **) calloc(AntPermLast, sizeof(float*));; the value between the second
* and the last
* in the line was italicised instead.
The code formatting is working entirely correctly here, your edits were wrong. By indenting the code properly it is being displayed as code instead of having it being interpreted as markdown-formatted text. That is why I rolled back your edit.