[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Dump file format

From: Dr . Jürgen Sauermann
Subject: Re: Dump file format
Date: Mon, 28 Oct 2019 12:22:36 +0100
User-agent: Mozilla/5.0 (X11; Linux i686; rv:60.0) Gecko/20100101 Thunderbird/60.6.1

Hi Blake,

there was actually a reason: the dump files are easier to read if the
function text between the two ∇ is indented (by one space). The change
I made to achieve that did not, however, properly handle already indented lines.

I have fixed this, similar to your previous suggestion, so that all lines are
now indented by exactly one space. SVN 1197.

Best Regards,
Jürgen Sauermann

On 10/27/19 7:25 PM, Blake McBride wrote:

I have a few workspaces on github in DUMP format.  I think it is a good idea for me to keep the format up-to-date.  While performing said update I noticed, what seems to be, an arbitrary change that causes nearly every line to change.

In the past, the dump file format placed a single space before every function body line.  That's fine.  However, for reason unknown, the DUMP format now puts two spaces before every function body line.  This seemingly arbitrary change causes git to see every line as changed.  Therefore, real changes are hard to spot.  (I know git has an ignore spaces option.  However, nevertheless, git sees and records each line as having changed.)

I suppose it doesn't matter which way it is.  It's just best if it didn't change without a good reason.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]