unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Problems stepping through PC-lint output
Date: Fri, 04 Nov 2005 13:04:57 +0200	[thread overview]
Message-ID: <uhdasvfl2.fsf@gnu.org> (raw)
In-Reply-To: <u4q6t5qn9.fsf@raytheon.com> (message from Sarir Khamsi on Thu, 03 Nov 2005 15:10:34 -0700)

> From: Sarir Khamsi <sarir.khamsi@raytheon.com>
> Date: Thu, 03 Nov 2005 15:10:34 -0700
> 
> I am using GNU Emacs (22.0.50.20) on WinXP, SP2

Problems with the CVS version of Emacs should be posted to
emacs-devel@gnu.org, not here.

> For example, given the lines
> 
>    --- Module:   Vehicle.cpp
>                _
>    #define D2R 0.0174532925199433
>    MathGlobals.h:41:12: Note 1923: macro 'D2R' could become const variable --
>        Effective C++ #1
>                  _
>    #define R2D 1/D2R
>    MathGlobals.h:42:14: Info 773: Expression-like macro 'R2D' not parenthesized
>    MathGlobals.h:42:14: Note 1923: macro 'R2D' could become const variable --
>        Effective C++ #1
>                       _
>       d_IParam(double);
>    ConcreteTypes.hpp:21:19: Note 1931: Constructor 'd_IParam::d_IParam(double)'
>        can be used for implicit conversions -- More Effective C++ #5
>                    _
>       i_IParam(int);
> 
> the "MathGlobals.h:42:14: Info 773" line will get skipped and Emacs
> will jump to the next message (in this case, the second "Note 1923"
> about R2D).

I suspect that this is because "info:" is special to the compilation
messages parser.  See the file etc/compilation.txt in the Emacs
distribution.

If you post this to emacs-devel, the Emacs developers will look at the
problem and try to fix it.

  reply	other threads:[~2005-11-04 11:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03 22:10 Problems stepping through PC-lint output Sarir Khamsi
2005-11-04 11:04 ` Eli Zaretskii [this message]
     [not found] ` <mailman.13922.1131102300.20277.help-gnu-emacs@gnu.org>
2005-11-04 17:17   ` Sarir Khamsi
2005-11-22 19:59 ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uhdasvfl2.fsf@gnu.org \
    --to=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).