This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 2/2] etc/texi2pod.pl: C<>'s can be nested as well
- From: Simon Marchi <simark at simark dot ca>
- To: Carl Bordum Hansen <carl at bordum dot dk>, gdb-patches at sourceware dot org
- Date: Mon, 16 Sep 2019 21:40:35 -0400
- Subject: Re: [PATCH 2/2] etc/texi2pod.pl: C<>'s can be nested as well
- References: <BX1RO04GX4C8.1F9RUUJRL3BIC@carl-T440p>
On 2019-09-16 6:06 p.m., Carl Bordum Hansen wrote:
> ---
> etc/texi2pod.pl | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/etc/texi2pod.pl b/etc/texi2pod.pl
> index 34ba7efd0f..167cc71ba9 100644
> --- a/etc/texi2pod.pl
> +++ b/etc/texi2pod.pl
> @@ -416,9 +416,9 @@ sub postprocess
> s/</</g;
> s/>/>/g;
>
> - # Now un-nest all B<>, I<>, R<>. Theoretically we could have
> + # Now un-nest all B<>, I<>, R<>, C<>. Theoretically we could have
> # indefinitely deep nesting; in practice, one level suffices.
> - 1 while s/([BIR])<([^<>]*)([BIR])<([^<>]*)>/$1<$2>$3<$4>$1</g;
> + 1 while s/([BIRC])<([^<>]*)([BIRC])<([^<>]*)>/$1<$2>$3<$4>$1</g;
>
> # Replace R<...> with bare ...; eliminate empty markup, B<>;
> # shift white space at the ends of [BI]<...> expressions outside
>
Hi Carl,
Can you explain why this change is needed? Is there a file that was not
generated properly?
Simon