ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Re: Announcement: texutil.c
Date: Fri, 19 Mar 2004 13:31:30 +0100	[thread overview]
Message-ID: <20040319133130.3ebb63ff.taco@elvenkind.com> (raw)
In-Reply-To: <405ABB01.5040900@voiceinterconnect.de>

On Fri, 19 Mar 2004 10:18:57 +0100
Uwe Koloska <koloska@voiceinterconnect.de> wrote:

> Taco Hoekwater wrote:
> > For a larger project with ConTeXt that should not depend on
> > the availability of perl. We needed a very large section of
> > Texutil (--ref and --figures), so it made sense to port the
> > entire program to C.
> 
> What about using another script language like TCL that can be
> made into a single file executable?  The dependency seems to be 

I knew how to get the job done quickly in C, not in TCL. 
Also there are some extra runtime requirements like: 
	"not bigger nor slower than necessary".

The C version runs quite a bit faster. The compiled C code is a 
lot smaller than including an interpreter. texutil.c links easily 
to tex.c (and tex.rb would have been a bit too much work ;)). etc.

Incidentally: yes, I have a tex.c. That may in fact become GPL-ed
sometime in the future, if and when our finished project deviates
sufficiently from tex.c+texutil.c

  parent reply	other threads:[~2004-03-19 12:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-17 14:10 Taco Hoekwater
2004-03-18 15:57 ` Patrick Gundlach
2004-03-19  8:14   ` Taco Hoekwater
2004-03-19  9:18     ` Uwe Koloska
2004-03-19  9:36       ` Hans Hagen
2004-03-19 12:56         ` Uwe Koloska
2004-03-19 13:32           ` Hans Hagen
2004-03-19 14:31             ` Tobias Burnus
2004-03-19 13:03         ` Uwe Koloska
2004-03-19 13:34           ` Hans Hagen
2004-03-19 12:31       ` Taco Hoekwater [this message]
2004-03-19 12:57         ` Uwe Koloska

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=20040319133130.3ebb63ff.taco@elvenkind.com \
    --to=taco@elvenkind.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).