From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: reducing compile time
Date: Mon, 23 Feb 2009 21:40:28 +0100 [thread overview]
Message-ID: <fe8d59da0902231240t2c6ae43fydf7e1d44c7797436@mail.gmail.com> (raw)
In-Reply-To: <326847810902231226v63744395y56374cec7f10b8eb@mail.gmail.com>
On Mon, Feb 23, 2009 at 9:26 PM, Alan Stone
<software.list.1es9s@gmail.com> wrote:
> On Mon, Feb 23, 2009 at 8:57 PM, Alan Stone <software.list.1es9s@gmail.com>
> wrote:
>>
>> 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.
>
>
> Correction: to avoid spending time redefining macros in case their
> definitions are kept in memory between Lua(TeX) runs.
$>context test.tex
is roughly
finish :=false
while not(finish):
run_luatex_with_context_format_on_file(test.tex)
where
run_luatex_with_context_format_on_file(filename)
is my imaginary name that
run luatex (for example on my system
luatex --fmt="/opt/luatex/minimals/tex/texmf-cache/luatex-cache/context/4330c3ed7721ca11f9d108c60c58eea4/formats/cont-en"
--lua="/opt/luatex/minimals/tex/texmf-cache/luatex-cache/context/4330c3ed7721ca11f9d108c60c58eea4/formats/cont-en.lua"
"./test.tex"
)
but also check conditions to that change
finish to true
and possible write intermediate files.
So,as far I know, each run is a new process: there is no a master
process that spawns new children ,
and no definitions are kept in memory between Lua(TeX) runs.
--
luigi
___________________________________________________________________________________
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 20:40 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
2009-02-23 20:26 ` Alan Stone
2009-02-23 20:40 ` luigi scarso [this message]
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=fe8d59da0902231240t2c6ae43fydf7e1d44c7797436@mail.gmail.com \
--to=luigi.scarso@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).