At 12:52 2007-01-30, L. Wayne Johnson wrote:
> >> >
> >> >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?
actually, _I_ wrote that
and you're waaaaaaay to hung up on standards
>The following are end of line characters I am aware of:
>
>Linux (Unix) : 0x0A
>DOS/Windows : Ox0D 0x0A
>MAC : 0x0D
Mac finally smartened up and now use 0x0A
>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.
and exactly what difference does it make editors should read any
kind of EOL and either retain what they get, or write in a consistant
(selectable) manner (my editors do...well except for the brain dead
stuff that MS writes)
>The point is that all of the decisions are perfectly valid if there's not
>standard.
what decisions? at it's POSSIBLE that maybe 0x0d 0x0a should be a
blank line?? all the other decisions treat lines "correctly"
>If you use more than one tool that decides to handle the line
>endings differently you can end up with undesirable results.
AS I SAID WHEN THIS ALL STARTED.... TOOLS THAT DO NOT TREAT ALL THE
LINE ENDINGS EQUIVALENTLY HAVE AN ARCHITECTURE/DESIGN FLAW.
you seem to want to take issue with the. I don't care HOW many
program you show that have architecture/design flaws, it doesn't
alter the fact that they're WRONG!!
> This is
>especially difficult when working in a cross platform situation.
it's only a problem really, because Microsoft has had their head up
their ass ever since they started releasing software.
>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.
nobody, and we've been trying to tell you (but you just don't "get
it") that there are editors that will give you very nice single
spaced lines no matter what EOL crap gets thrown at them. Except for
the editor I kinda have to use in Visual Studio, ALL my editors
treat 0x0A; 0x0D 0x0A; and 0x0D as "line markers" on input (for
all I know, they also accept 0x0A 0x0D.
none of the screen images are all joined together nor double spaced.
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
Victor A. Wagner Jr. http://rudbek.com
The five most dangerous words in the English language:
"There oughta be a law"
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 31 05:07:04 2007