[Top][All Lists]

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

Re: [help-texinfo] texi2dvi: AUC-TeX and depots

From: Akim Demaille
Subject: Re: [help-texinfo] texi2dvi: AUC-TeX and depots
Date: Wed, 21 Sep 2005 09:26:05 +0200
User-agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux)

>>> "Karl" == Karl Berry <address@hidden> writes:

 >      neither --directory, too meaningless.
 > True, but I still prefer --directory to any of the other suggestions.
 > At least it exists with a vaguely similar meaning in other programs.
 > Ok?

I was also using depot because I saw it in a somewhat similar
situation: CFront's instantiation of templates.  Actually it is
`repository' that was used:
Cfront model
    The AT&T C++ translator, Cfront, solved the template instantiation
    problem by creating the notion of a template *repository*, an
    automatically maintained place where template instances are
    stored. A more modern version of the *repository* works as follows:
    As individual object files are built, the compiler places any
    template definitions and instantiations encountered in the
    *repository*. At link time, the link wrapper adds in the objects in
    the *repository* and compiles any needed instances that were not
    previously emitted. The advantages of this model are more optimal
    compilation speed and the ability to use the system linker; to
    implement the Borland model a compiler vendor also needs to
    replace the linker. The disadvantages are vastly increased
    complexity, and thus potential for error; for some code this can
    be just as transparent, but in practice it can been very difficult
    to build multiple programs in one directory and one program in
    multiple directories. Code written for this model tends to
    separate definitions of non-inline member templates into a
    separate file, which should be compiled separately.


Mac OSX's modified GCC also supports this word:
To create the symbol repository for a header file foo.h, use the following 

    gcc-3.3 <other flags> -fsave-repository=cinfo_dir_name  foo.h  

This command will create two files:

    * foo.cinfo in the cinfo_dir_name directory.
    * An output file, which by default is foo.h.o in the current
      folder. As usual, the name and location can be changed from the
      default by explicitly using the -o compiler flag. 

To use the repository in subsequent compilations, you must provide the
-grepository command line option. The compiler will then search for
.cinfo files in all include paths.

I have one suggestion we might agree upon: --build-dir.  After all,
that's the name of the internal variable, and also of the envvar!

 > But they might believe it will somehow automatically check out files.
 > That's the first thing I thought when I saw the name, and wondered what
 > Akim was up to now :).

Actually, that's a nice idea.  I'll try to dig it ;)

 >     I agree pdftexi2dvi is bad, but that's really how AUC-TeX works --

 > Oh, very well, I don't really agree with your arguments, but I give in
 > on this one anyway.  Bah, humbug :).

:) :) :)

reply via email to

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