From: Hans Hagen <pragma@wxs.nl>
Cc: "eckhart Guthöhrlein"
<eckhart_guthoehrlein@public.uni-hamburg.de>,
"ConTeXt mailing list" <ntg-context@ntg.nl>
Subject: Re: problem with texexec and inline metapost
Date: Mon, 16 Jul 2001 09:36:56 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20010716093507.02ef4280@server-1> (raw)
In-Reply-To: <5.1.0.14.0.20010714182604.00aa4170@public.uni-hamburg.de>
At 06:27 PM 7/14/2001 +0200, Eckhart Guthöhrlein wrote:
>At 12:57 14.07.2001 +0200, you wrote:
>>Eckhart Guthöhrlein wrote:
>> >
>> > But what about having texexec/perl calculate the checksums, writing
>> them to
>> > an auxiliary file, and tex just reading them? And in any case, one can be
>> > sure that the mp code will not change during the same call to texexec (or
>> > can there be exceptions?), so that if, say, three tex runs are necessary,
>> > one run of mp would be sufficient. Setting some switch may be
>> sufficient to
>> > achieve this.
>>
>>It *can* change with a texexec, imagine using the page number in the MP
>>code, for example. More serious problem: even if texexec calculates the
>>checksum, then how would the TeX macro code know its status without
>>first
>>calculating a checksum itself? It needs to compare two checksums: one
>>from
>>this run against the one from the previous run.
>
>So, why not keeping two checksums in the aux file? No, no, all right, I
>admit that I did not think beyond my simple applications. Metapost is
>actually quite fast, so I must agree with yoz that the additional gain of
>speed (maybe even not...) is probably not worth the trouble. And it is
>likely that there will be more problems than positive effects and than I
>can imagine... So let's forget about it, it was just an idea, coming up
>because my - until recently - preferred method texexec --automprun does
>not work as expected at the moment (see the other thread).
much faster processing can be achieved with mp as dll and kpsea as server
app [only have file base in mem once], which is something fptex wizard
fabrice popineau is thinking/working about/on.
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-07-16 7:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-14 16:27 Eckhart Guthöhrlein
2001-07-16 7:36 ` Hans Hagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-03 18:01 Eckhart Guthöhrlein
2001-07-04 6:47 ` Hans Hagen
2001-07-04 7:30 ` Eckhart Guthöhrlein
2001-07-14 10:02 ` Eckhart Guthöhrlein
2001-07-14 10:35 ` Taco Hoekwater
2001-07-14 10:38 ` Eckhart Guthöhrlein
2001-07-14 10:57 ` Taco Hoekwater
2001-07-16 7:33 ` 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=5.1.0.14.1.20010716093507.02ef4280@server-1 \
--to=pragma@wxs.nl \
--cc=eckhart_guthoehrlein@public.uni-hamburg.de \
--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).