Tweet
Incorrect mismatch on pathologically-long lines.
(Sorry folks, I don't create these files, I just try to wrangle them 
.)
I'm comparing using BC3 to compare to versions of a very simple JavaScript file and a "mismatch" is getting falsely flagged.
Basically, my files are as follows:
Where the literal string "..." is really 4100 bytes of "." (or any other string characters that you like).
In one version of the file, that string is indented using 7 {tab} characters. In the other version of the file, the indent is made using 28 {space} characters. Therefore, these files are only "insignificantly" different.
But apparently because BC3 starts to wrap text in the display panes once the lines exceed about 4096 characters, it ends up wrapping a different amount of text for the "tabbed" version as compared to the "spaced" version. It then calls those "wrapped" lines different.
Here's a simulated screen shot of the two panes:
From the pane displaying the "tabbed" file:
From the pane displaying the "spaced" file:
Don't feel too bad about this, because, for example, vim's syntax analyzer gives up after only 3,000 bytes of this ridiculous string, displaying the rest as if they weren't part of the literal string. And I'll have a conversation with my developers about using such pathological constructs.
But meanwhile, I thought you'd like to know about this limitation in BC3.
Atlant
.)I'm comparing using BC3 to compare to versions of a very simple JavaScript file and a "mismatch" is getting falsely flagged.
Basically, my files are as follows:
Code:
var my_array = new Array(
"...";
)
In one version of the file, that string is indented using 7 {tab} characters. In the other version of the file, the indent is made using 28 {space} characters. Therefore, these files are only "insignificantly" different.
But apparently because BC3 starts to wrap text in the display panes once the lines exceed about 4096 characters, it ends up wrapping a different amount of text for the "tabbed" version as compared to the "spaced" version. It then calls those "wrapped" lines different.
Here's a simulated screen shot of the two panes:
From the pane displaying the "tabbed" file:
var my_array = new Array(............"
);
"........................
);
From the pane displaying the "spaced" file:
var my_array = new Array(................................."
);
"........................
);
Don't feel too bad about this, because, for example, vim's syntax analyzer gives up after only 3,000 bytes of this ridiculous string, displaying the rest as if they weren't part of the literal string. And I'll have a conversation with my developers about using such pathological constructs.
But meanwhile, I thought you'd like to know about this limitation in BC3.
Atlant
Comment