unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: 6414@debbugs.gnu.org
Subject: bug#6414: f->output_data.w32->menubar_widget uninitialized?
Date: Mon, 4 Jul 2011 04:13:32 +0200	[thread overview]
Message-ID: <CAAeL0STru8Y7yA3OJEL=Lp0gsWg85SNwPeJZ7L2Oz1MiaR2b=g@mail.gmail.com> (raw)
In-Reply-To: <CANbX364nvQBnU9ADOPuVsJmw0V1xvwbwNs=wDF+9KBJ_kYqq2w@mail.gmail.com>

On Mon, Jul 4, 2011 at 03:44, Lennart Borgman <lennart.borgman@gmail.com> wrote:

> A debug message could still help.

Yes. Or difficult debugging of other issues. Depends on the debug
message, its frequency and relevancy.

> A bad assumption in my book.

Well, we can disagree.

> Yes, it is extra complexity. But I think the extra complexity that is
> the result of not doing this error checking is much, much worse. There
> might be very serious troubles and you have no idea what it is.

If there are "serious troubles" and nobody ever notices them, then
they are not "serious troubles". We're talking about Emacs, not real
time avionics or nuclear plant control software.

> Could you please check the MS doc and see if these calls should be
> switched?

No. You're the one who's spent time looking at the menu code. You're
the one who should know whether that is really a bug and propose a
patch.

    Juanma





  reply	other threads:[~2011-07-04  2:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-13 18:01 bug#6414: f->output_data.w32->menubar_widget uninitialized? Lennart Borgman
2010-06-13 18:32 ` Lennart Borgman
2010-06-13 18:47   ` Lennart Borgman
2011-07-03 18:54     ` Juanma Barranquero
2011-07-03 22:19       ` Lennart Borgman
2011-07-03 22:30         ` Juanma Barranquero
2011-07-03 22:37           ` Lennart Borgman
2011-07-03 22:48             ` Juanma Barranquero
2011-07-03 23:11               ` Lennart Borgman
2011-07-03 23:21                 ` Juanma Barranquero
2011-07-03 23:42                   ` Lennart Borgman
2011-07-04  0:34                     ` Juanma Barranquero
2011-07-04  1:08                       ` Lennart Borgman
2011-07-04  1:21                         ` Juanma Barranquero
2011-07-04  1:44                           ` Lennart Borgman
2011-07-04  2:13                             ` Juanma Barranquero [this message]
2011-07-04  2:18                               ` Lennart Borgman
2011-07-04  2:35                                 ` Juanma Barranquero
2011-09-21 20:32                                   ` Lars Magne Ingebrigtsen
2011-09-21 20:40                                     ` Lennart Borgman
2011-09-21 20:44                                       ` Juanma Barranquero
2011-09-21 20:46                                         ` Lennart Borgman
2011-09-21 20:59                                           ` Lars Magne Ingebrigtsen
2011-09-21 21:07                                             ` Lennart Borgman

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='CAAeL0STru8Y7yA3OJEL=Lp0gsWg85SNwPeJZ7L2Oz1MiaR2b=g@mail.gmail.com' \
    --to=lekktu@gmail.com \
    --cc=6414@debbugs.gnu.org \
    --cc=lennart.borgman@gmail.com \
    /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.
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).