unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#22019: 25.0.50; Bad comment in `character-fold-to-regexp'
@ 2015-11-26 23:03 Drew Adams
  2015-11-26 23:40 ` Artur Malabarba
  2015-11-27  6:38 ` Richard Stallman
  0 siblings, 2 replies; 4+ messages in thread
From: Drew Adams @ 2015-11-26 23:03 UTC (permalink / raw)
  To: 22019

This part of an explanatory comment is inadequate and inappropriate:

 ;; See commit message for a longer description.

What commit message?  The source code should contain the description.
If a VC commit message happens to also contain the description, so
much the better for it.  But that doesn't help a reader of the code.

This comment is intended to make clear what the design/intention is.
Readers of the source code deserve the additional design information
as much as maintainers who might bother to access the relevant commit.


In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
 of 2015-11-12
Bzr revision: 6e5186e8a7ccfb9b8fb35b5f4f0371e4f4a68162
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/Devel/emacs/snapshot/trunk
 --enable-checking=yes,glyphs --enable-check-lisp-object-type
 --without-compress-install --with-wide-int 'CFLAGS=-O0 -ggdb3'
 LDFLAGS=-Lc:/Devel/emacs/lib 'CPPFLAGS=-DGC_MCHECK=1
 -Ic:/Devel/emacs/include''





^ permalink raw reply	[flat|nested] 4+ messages in thread

* bug#22019: 25.0.50; Bad comment in `character-fold-to-regexp'
  2015-11-26 23:03 bug#22019: 25.0.50; Bad comment in `character-fold-to-regexp' Drew Adams
@ 2015-11-26 23:40 ` Artur Malabarba
  2015-11-27  6:38 ` Richard Stallman
  1 sibling, 0 replies; 4+ messages in thread
From: Artur Malabarba @ 2015-11-26 23:40 UTC (permalink / raw)
  To: Drew Adams; +Cc: 22019

[-- Attachment #1: Type: text/plain, Size: 682 bytes --]

On 26 Nov 2015 11:03 pm, "Drew Adams" <drew.adams@oracle.com> wrote:
>
> This part of an explanatory comment is inadequate and inappropriate:
>
>  ;; See commit message for a longer description.
>
> What commit message?  The source code should contain the description.
> If a VC commit message happens to also contain the description, so
> much the better for it.  But that doesn't help a reader of the code.

Maybe I'm just a little too acostumed to the convenience of magit-blame.
Commit messages are the first place I look when I don't understand the
code. But I understand that doesn't help readers who are not reading
directly from the repo, so a better comment would be nice.

[-- Attachment #2: Type: text/html, Size: 866 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* bug#22019: 25.0.50; Bad comment in `character-fold-to-regexp'
  2015-11-26 23:03 bug#22019: 25.0.50; Bad comment in `character-fold-to-regexp' Drew Adams
  2015-11-26 23:40 ` Artur Malabarba
@ 2015-11-27  6:38 ` Richard Stallman
  2015-11-27  8:54   ` Eli Zaretskii
  1 sibling, 1 reply; 4+ messages in thread
From: Richard Stallman @ 2015-11-27  6:38 UTC (permalink / raw)
  To: Drew Adams; +Cc: 22019

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > This part of an explanatory comment is inadequate and inappropriate:

  >  ;; See commit message for a longer description.

That's right.  GNU standard practices say the place to put
an explanation is in a comment, not in a change log.

Can someone please fix this one now?  We shouldn't leave this
dirty in the sink overnight.

-- 
Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.






^ permalink raw reply	[flat|nested] 4+ messages in thread

* bug#22019: 25.0.50; Bad comment in `character-fold-to-regexp'
  2015-11-27  6:38 ` Richard Stallman
@ 2015-11-27  8:54   ` Eli Zaretskii
  0 siblings, 0 replies; 4+ messages in thread
From: Eli Zaretskii @ 2015-11-27  8:54 UTC (permalink / raw)
  To: rms; +Cc: 22019

> From: Richard Stallman <rms@gnu.org>
> Date: Fri, 27 Nov 2015 01:38:33 -0500
> Cc: 22019@debbugs.gnu.org
> 
>   > This part of an explanatory comment is inadequate and inappropriate:
> 
>   >  ;; See commit message for a longer description.
> 
> That's right.  GNU standard practices say the place to put
> an explanation is in a comment, not in a change log.
> 
> Can someone please fix this one now?

Done.





^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2015-11-27  8:54 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-11-26 23:03 bug#22019: 25.0.50; Bad comment in `character-fold-to-regexp' Drew Adams
2015-11-26 23:40 ` Artur Malabarba
2015-11-27  6:38 ` Richard Stallman
2015-11-27  8:54   ` Eli Zaretskii

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).