>> >
>> >When you find the standard that describes what the debugger is doing
>> >wrong, please quote it. I'm not aware of any that demand
>> >recognition of non-native line endings on any platform.
>>
>> there IS no standard for the damned debugger..... YOU HAVE A BROKEN
>> SYSTEM
>> I'm SO sorry, bitch at the damned ARM developers
>>
>>
Unless you come up with a standard for handling mixed line endings how can
you possibly handle them consistently?
The following are end of line characters I am aware of:
Linux (Unix) : 0x0A
DOS/Windows : Ox0D 0x0A
MAC : 0x0D
So is 0x0A 0x0D a single Windows EOL or a Linux file edited on a MAC or a
MAC file edited on Linux? This is a trivial example but I am sure that with
a little bit of time I can come up with a more substantive example.
The point is that all of the decisions are perfectly valid if there's not
standard. If you use more than one tool that decides to handle the line
endings differently you can end up with undesirable results. This is
especially difficult when working in a cross platform situation. When you
can ignore white space this is not a problem. However, you can't always
ignore white space...
Who would use and editor that gave you this:
int i;int
j;for(i=10;i<10;i++){j=calc(i);j+=calc(i-global_valud);if(j>=maxval)break;}
or even this:
int i;
int j;
for(i=10;i<10;i++){
j=calc(i);
j+=calc(i-global_valud);
if(j>=maxval)
break;
}
>From the exact same input.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 30 20:52:33 2007