Re: Form feeds in source code

2020-09-18 Thread Pete Dietl
Alright I concede. As long as people are getting use out of them and they are not vestigial, then they have reason to stay of course. On Fri, Sep 18, 2020 at 2:57 PM Eli Zaretskii wrote: > > From: Pete Dietl > > Date: Fri, 18 Sep 2020 14:33:58 -0500 > > Cc: bug-make , Edward Welbourne < >

Re: Form feeds in source code

2020-09-18 Thread Eli Zaretskii
> From: Pete Dietl > Date: Fri, 18 Sep 2020 11:27:18 -0500 > Cc: "p...@mad-scientist.net" , > bug-make > > I think keeping them in for the sake of one editor is not a good reason. I > think they make the code look messy > and dated, personally. With all due respect, Emacs is not just "one

Re: Form feeds in source code

2020-09-18 Thread Eli Zaretskii
> From: Pete Dietl > Date: Fri, 18 Sep 2020 14:33:58 -0500 > Cc: bug-make , Edward Welbourne , > p...@mad-scientist.net > > Would it also be a reasonable request then to add in vim markers for custom > folding or indentation/formatting > directives? Why not? > Also, the space between form

Re: Form feeds in source code

2020-09-18 Thread Pete Dietl
I was not intending to offend anyone. I literally meant that emacs is an editor among many. Would it also be a reasonable request then to add in vim markers for custom folding or indentation/formatting directives? Also, the space between form feeds sometimes goes well beyond a typical terminal

Re: Form feeds in source code

2020-09-18 Thread Daniel Herring
While I sympathise with the request to leave them be, most editors do not support jumping by ff-marked pages and emacs has other ways to jump to function definitions. If this use of the form feed ever regains widespread use, I suspect it would come in the form of a new Unicode character. -

Re: Form feeds in source code

2020-09-18 Thread Pete Dietl
I think keeping them in for the sake of one editor is not a good reason. I think they make the code look messy and dated, personally. On Fri, Sep 18, 2020 at 11:24 AM Edward Welbourne wrote: > On Fri, 2020-09-18 at 10:59 -0500, Pete Dietl wrote: > > >> Why are there so many form feeds in the

Re: Form feeds in source code

2020-09-18 Thread Edward Welbourne
On Fri, 2020-09-18 at 10:59 -0500, Pete Dietl wrote: >> Why are there so many form feeds in the source? Paul Smith (18 September 2020 18:12) replied: > That was the style that Roland used when the code was written: form > feeds were used inside a source file to separate major functions. > > I

Re: Form feeds in source code

2020-09-18 Thread Blake McBride
In the old days, with limited memory, editors would only read a file up to the formfeed. The programmer would edit the text up to the formfeed and then read in the next block (up to the next formfeed). This way the whole file need not be in memory at once. Compilers ignore it. Obviously they

Re: Form feeds in source code

2020-09-18 Thread Pete Dietl
So I’m free to submit a patch to delete these? :) On Fri, Sep 18, 2020 at 11:12 AM Blake McBride wrote: > In the old days, with limited memory, editors would only read a file up to > the formfeed. The programmer would edit the text up to the formfeed and > then read in the next block (up to

Re: Form feeds in source code

2020-09-18 Thread Paul Smith
On Fri, 2020-09-18 at 10:59 -0500, Pete Dietl wrote: > Why are there so many form feeds in the source? That was the style that Roland used when the code was written: form feeds were used inside a source file to separate major functions. I guess it hails from a time when it wasn't that unusual to

Form feeds in source code

2020-09-18 Thread Pete Dietl
Why are there so many form feeds in the source? Running this from the root of the Make repo: cd src && grep -c $'\f' *.[ch] | grep -v ':0$' | sort -t : -k 2 -n -r | awk -F : 'BEGIN {printf "%-15s Number of form feeds\n", "File"; print "" } {printf "%-15s