public inbox for newlib-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jturney@sourceware.org>
To: newlib-cvs@sourceware.org
Subject: [newlib-cygwin] fenv: Update makedocbook for eae68bfc
Date: Tue, 13 Aug 2019 11:31:00 -0000	[thread overview]
Message-ID: <20190813113120.63193.qmail@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=8922b85d6bb5072441468ea24e764a825b9e1d9f

commit 8922b85d6bb5072441468ea24e764a825b9e1d9f
Author: Jon Turney <jon.turney@dronecode.org.uk>
Date:   Mon Aug 12 19:27:10 2019 +0100

    fenv: Update makedocbook for eae68bfc
    
    Teach makedocbook how to handle some new things seen in the makedoc markup
    since eae68bfc:
    - 'link with' lines appearing in SYNOPSIS sections
    
    Also, don't raise a NoneType exception when there's something we don't
    know how to handle in a SYNOPSIS section, just exit.

Diff:
---
 newlib/doc/makedocbook.py | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/newlib/doc/makedocbook.py b/newlib/doc/makedocbook.py
index cf48c34..9725534 100755
--- a/newlib/doc/makedocbook.py
+++ b/newlib/doc/makedocbook.py
@@ -297,6 +297,8 @@ def synopsis(c, t):
 	    # preprocessor # directives, structs, comments in square brackets
 	    funcsynopsisinfo = lxml.etree.SubElement(funcsynopsis, 'funcsynopsisinfo')
 	    funcsynopsisinfo.text = l.strip() + '\n'
+	elif re.match('[Ll]ink with', l):
+	    pass
 	else:
 	    s = s + l
 
@@ -312,7 +314,7 @@ def synopsis(c, t):
 
     if s.strip():
 	print("surplus synopsis '%s'" % s, file=sys.stderr)
-	raise
+	exit(1)
 
 def synopsis_for_prototype(funcsynopsis, s):
     s = s.strip()


                 reply	other threads:[~2019-08-13 11:31 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=20190813113120.63193.qmail@sourceware.org \
    --to=jturney@sourceware.org \
    --cc=newlib-cvs@sourceware.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).