From: Alan Stone <software.list.1es9s@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: reducing compile time
Date: Mon, 23 Feb 2009 20:57:56 +0100 [thread overview]
Message-ID: <326847810902231157kc49bd83i8df988abc0ee28be@mail.gmail.com> (raw)
In-Reply-To: <FBAA9400-1D8B-4826-A33E-A1A16E114DCF@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 729 bytes --]
On Mon, Feb 23, 2009 at 6:54 PM, Wolfgang Schuster <
schuster.wolfgang@googlemail.com> wrote:
>
> Am 23.02.2009 um 18:16 schrieb Alan Stone:
>
> - does using \doifundefined{myMacro}{...} shorten tex runs/compile time ?
>>
>
> In which way?
As I don't know/understand what happens between (Lua)TeX runs, to keep macro
definitions in memory.
- what are the features to avoid for shortest compile times ?
>
> Depends on your document and what do you want.
My question was intended in a generic way, aka if you use
- these features ... expect longer or significant longer compile times, or
- these features ... generate the longest compile times.
> To give you a better answer speak in complete sentences.
>
> Wolfgang
>
>
[-- Attachment #1.2: Type: text/html, Size: 1563 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-02-23 19:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 17:16 Alan Stone
2009-02-23 17:36 ` Alan Stone
2009-02-23 17:54 ` Wolfgang Schuster
2009-02-23 19:57 ` Alan Stone [this message]
2009-02-23 20:26 ` Alan Stone
2009-02-23 20:40 ` luigi scarso
2009-02-23 23:34 ` Hans Hagen
2009-02-23 20:37 ` Wolfgang Schuster
2009-02-23 18:38 ` Taco Hoekwater
2009-02-23 23:00 ` Mohamed Bana
2009-02-24 8:10 ` Taco Hoekwater
2009-02-24 8:48 ` Hans Hagen
2009-02-23 23:27 ` Hans Hagen
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=326847810902231157kc49bd83i8df988abc0ee28be@mail.gmail.com \
--to=software.list.1es9s@gmail.com \
--cc=ntg-context@ntg.nl \
/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).