From: joerg@mdocml.bsd.lv
To: source@mdocml.bsd.lv
Subject: mdocml: Convert an assert into an explicit check.
Date: Fri, 18 Nov 2011 11:39:08 -0500 (EST) [thread overview]
Message-ID: <201111181639.pAIGd8Y3022061@krisdoz.my.domain> (raw)
Log Message:
-----------
Convert an assert into an explicit check. man_unscope can be triggered
on unknown macros.
Modified Files:
--------------
mdocml:
man_macro.c
Revision Data
-------------
Index: man_macro.c
===================================================================
RCS file: /home/joerg/cvsroot/mdocml/man_macro.c,v
retrieving revision 1.66
retrieving revision 1.67
diff -Lman_macro.c -Lman_macro.c -u -p -r1.66 -r1.67
--- man_macro.c
+++ man_macro.c
@@ -120,7 +120,8 @@ man_unscope(struct man *m, const struct
assert(to);
- assert(MAN_ROOT != m->last->type);
+ if (MAN_ROOT != m->last->type)
+ return(0);
m->next = MAN_NEXT_SIBLING;
/* LINTED */
--
To unsubscribe send an email to source+unsubscribe@mdocml.bsd.lv
reply other threads:[~2011-11-18 16:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201111181639.pAIGd8Y3022061@krisdoz.my.domain \
--to=joerg@mdocml.bsd.lv \
--cc=source@mdocml.bsd.lv \
/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 NNTP newsgroup(s).