[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [OctDev] munge-texi problem with static library build

From: Daniel J Sebald
Subject: Re: [OctDev] munge-texi problem with static library build
Date: Wed, 16 Mar 2011 02:07:12 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Thunderbird/3.1.7

On 03/16/2011 01:21 AM, Rob Frohne wrote:
Hi Dan,

I added the \end to get out of tex. It wasn't from munge-texi.

arith-texi-t is empty.

Hmm, well munge-texi is a C++ program:


I search for "invalid doc file format" and see that munge-texi strips the comments then looks for doc delimiter symbol. If no match, then the file isn't processed. Hence, empty log file.

But what has me wondering is that

static const char doc_delim = '';

Without compiling or looking at K&R definition, I assume the delimiter symbol is a 0, i.e., '' is the same as '\0'. But I'm not following what this comparison is supposed to mean then:

      if (infile.get () != doc_delim)
         fatal ("invalid doc file format");

Looking for a null character?

Anyway, the skip_comments routine of munge-texi.cc looks for '#' as comment lines, but clearly arith.txi does not have '#' as a comment line. So maybe that is where the process is failing.

Or maybe there is something with DOCSTRINGS that is missing. Here are the inputs to munge-texi:

    top_srcdir = *++argv;

    while (*++argv)
      process_doc_file (*argv);

    process_texi_input_file (std::cin, std::cout);

In your expression ../.. is the top_srcdir, then


are "doc" files and then '< arith.txi' is the std_cin and '> arith.texi-t' is the std:cout. So what do your DOCSTRINGS files look like? Those don't appear in the repository so must be generated.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]