Phobos unit testing uncovers a CPU bug
Jonathan M Davis
jmdavisProg at gmx.com
Mon Nov 29 22:00:19 PST 2010
On Monday 29 November 2010 21:30:31 so at so.do wrote:
> > LOL. I couldn't figure out what was different about those lines (the
> > extra space
> > apparently; the fact that the text isn't monospaced makes it harder to
> > see
> > though). But no one's over going to get people to agree on spacing any
> > more than
> > they'll get them to agree on braces. Personally, I generally don't have
> > extraneous spaces but will periodically line up variable declarations
> > with
> > regards to names (which would require no work here because they're all
> > auto and
> > line up anyway). Other folks I know insist on always putting extra
> > spaces after
> > keywords like if and/or putting extra spaces before or after parens.
> > Trying to
> > convince anyone about spacing is a waste of time, and I'd say that
> > suggesting
> > that spacing be altered in code is generally a waste of time unless
> > there's
> > something abnormally bad about it (like 10 spaces after every paren or
> > something
> > ridiculous like that).
> >
> > - Jonathan M Davis
>
> IMHO this is a good example why inconsistencies are sometimes necessary.
> I don't put spaces into random places either but this example is crying
> for attention :)
If you say so. I don't see any problem with it. I can see why you'd want to add
the extra spaces (at least, once I put it in an editor with a monospaced font),
but I wouldn't have thought that it would be worth calling someone on it. It
just seems nitpicky, honestly.
- Jonathan M Davis
More information about the Digitalmars-d-announce
mailing list