Mark Atwood :
> Did Dr Mills have a preferred C style? If he did, was it not terrible?
It's in devel/dot.emacs. The codebase is in fact almost entirely formatted
this way; I've been careful to preserve that despite personally having
different preferences.
;; This is how Dave Mills likes to see
Interesting. He makes good points, and I have earned a living coding in
Ada, myself. But all that said, there are sufficient good reasons not to
port to Ada. Well, unless and until the DOD, the ARPA, or the
Physikalisch-Technische Bundesanstalt want to pay us enough to do it, at
which point it can
I'm not going to dictat my own style just because it's my style. But I
will veto tab characters, and 8 space tab stops, for all the reasons.
ANSI, modified K&R, OTBS, linux kernel style, uncrustify default, they are
all good to me.
..m
On Thu, Jan 5, 2017 at 11:58 AM Gary E. Miller wrote:
> Y
Yo Mark!
On Thu, 05 Jan 2017 19:32:55 +
Mark Atwood wrote:
> What is everyone else's preferred C indent style?
I'm stuck in the past, with s slightly modified K&R style.
> I have my own favorite, but I'm not the one who has to read and
> rework the C code.
I find any consistent style work
fallenpega...@gmail.com said:
> Did Dr Mills have a preferred C style? If he did, was it not terrible?
Yes. One of the extra files used to setup emacs to do the right thing.
I think it indented each level by a full 8-space tab stop.
> What is everyone else's preferred C indent style?
2 or 4
Did Dr Mills have a preferred C style? If he did, was it not terrible?
What is everyone else's preferred C indent style?
I have my own favorite, but I'm not the one who has to read and rework the
C code.
..m
On Thu, Jan 5, 2017 at 11:18 AM Daniel Poirot wrote:
> Before long, everyone will be
Before long, everyone will be using a virtual machine with an
integrated editor and common development system!
...oh, wait, that's what started all this:
https://en.wikipedia.org/wiki/Lisp_machine
On Thu, Jan 5, 2017 at 12:54 PM, Eric S. Raymond wrote:
> Hal Murray :
>>
>> >> Running uncr
Hal Murray :
>
> >> Running uncrustify against NTPsec is good idea, but it needs to
> >> be a flag day, because it will be a huge patch.
>
> > ...pretty much a 'fork' from which there is no recovery...
>
> Is that a serious problem? If so, why?
>
> It would mean that I couldn't (usefully) di
>> Running uncrustify against NTPsec is good idea, but it needs to
>> be a flag day, because it will be a huge patch.
> ...pretty much a 'fork' from which there is no recovery...
Is that a serious problem? If so, why?
It would mean that I couldn't (usefully) diff versions of a file that cros
On Thu, Jan 05, 2017 at 08:00:59AM -0500, Eric S. Raymond wrote:
> Therefor, you need not fix this one category of POP8 violation. If
> you think you can rearrange imports to make groups of them more
> coherent, go ahead and do that.
I only fixed it because it was the last of it's kind and I wa
Matt, devel/hacking.txt says:
Please read https://www.python.org/dev/peps/pep-0008/[PEP 8] and use
that style. The only PEP 8 style rule we relax is that you may
specify multiple module names in an import rather than going strictly
with one per line. The point is to encourage you
11 matches
Mail list logo
